Stéphane Tailland
67a080ac3b
Produced by k8s-platform/tools/generate-mcp-tools.py: deck file openapi2mcp does the conversion, and the wrapper re-injects the five things Kong's generator cannot emit — per-tool ACLs, the MCP behavioural annotations, the response schemas the plugin uses for structuredOutput, the real upstream host, and JSON-only request bodies. Each is a documented gap; see k8s-platform/MCP-TOOL-GENERATION.md. tools-policy.yaml carries the ACLs and doubles as the allow-list: an operation becomes a tool only if the policy names it. Kong would otherwise expose every operation in the spec, DELETE included, and can express no authorization at all from a bearer-token spec — silently, exit 0, no warning. Same tools as before, same ACLs. What changed: query parameters are now declared and callable, each tool carries its response schema so calls return structured content instead of raw JSON, and request bodies are no longer tripled across three identical content types. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
228 lines
6.5 KiB
YAML
228 lines
6.5 KiB
YAML
# GENERATED — do not edit. Edit openapi.yaml or tools-policy.yaml, then:
|
|
# k8s-platform/tools/generate-mcp-tools.py <this domain>
|
|
#
|
|
# Produced by `deck file openapi2mcp`, then post-processed to add the ACLs,
|
|
# the MCP behavioural annotations, the response schemas, the real upstream
|
|
# host and the JSON-only bodies that Kong's generator does not emit. Each of
|
|
# those is a documented gap — see k8s-platform/MCP-TOOL-GENERATION.md.
|
|
apiVersion: configuration.konghq.com/v1
|
|
kind: KongPlugin
|
|
metadata:
|
|
name: ${NAME}-payments-mcp-ai-mcp-proxy
|
|
namespace: ${NAMESPACE}
|
|
plugin: ai-mcp-proxy
|
|
config:
|
|
mode: conversion-listener
|
|
include_consumer_groups: true
|
|
tools:
|
|
- annotations:
|
|
title: List all payments
|
|
read_only_hint: true
|
|
idempotent_hint: true
|
|
destructive_hint: false
|
|
open_world_hint: false
|
|
description: Retrieve a paginated list of all customer payment records with amounts and dates.
|
|
method: GET
|
|
name: list-payments
|
|
parameters:
|
|
- description: A page number within the paginated result set.
|
|
in: query
|
|
name: page
|
|
required: false
|
|
schema:
|
|
type: integer
|
|
- description: Number of results to return per page.
|
|
in: query
|
|
name: page_size
|
|
required: false
|
|
schema:
|
|
type: integer
|
|
path: /payments/v1/payments/
|
|
acl:
|
|
allow:
|
|
- admin
|
|
- read_only
|
|
- product_manager
|
|
- customer
|
|
- support
|
|
scheme: http
|
|
host: ${REST_HOSTNAME}
|
|
responses:
|
|
'200':
|
|
content:
|
|
application/json:
|
|
schema:
|
|
type: object
|
|
properties:
|
|
count:
|
|
type: integer
|
|
example: 123
|
|
next:
|
|
type: string
|
|
nullable: true
|
|
format: uri
|
|
example: http://api.example.org/accounts/?page=4
|
|
previous:
|
|
type: string
|
|
nullable: true
|
|
format: uri
|
|
example: http://api.example.org/accounts/?page=2
|
|
results:
|
|
type: array
|
|
items:
|
|
type: object
|
|
description: Customer payment records
|
|
properties:
|
|
id:
|
|
type: integer
|
|
readOnly: true
|
|
checknumber:
|
|
type: string
|
|
maxLength: 50
|
|
paymentdate:
|
|
type: string
|
|
format: date
|
|
amount:
|
|
type: string
|
|
format: decimal
|
|
pattern: ^-?\d{0,8}(?:\.\d{0,2})?$
|
|
customernumber:
|
|
type: integer
|
|
maximum: 2147483647
|
|
minimum: -2147483648
|
|
required:
|
|
- amount
|
|
- checknumber
|
|
- customernumber
|
|
- id
|
|
- paymentdate
|
|
- annotations:
|
|
title: Get a specific payment
|
|
read_only_hint: true
|
|
idempotent_hint: true
|
|
destructive_hint: false
|
|
open_world_hint: false
|
|
description: Retrieve detailed information about a specific payment by customer number and check number.
|
|
method: GET
|
|
name: get-payment
|
|
parameters:
|
|
- description: The check number
|
|
in: path
|
|
name: checknumber
|
|
required: true
|
|
schema:
|
|
type: string
|
|
- description: The customer number
|
|
in: path
|
|
name: customernumber
|
|
required: true
|
|
schema:
|
|
type: integer
|
|
path: /payments/v1/payments/{customernumber}/{checknumber}/
|
|
acl:
|
|
allow:
|
|
- admin
|
|
- read_only
|
|
- product_manager
|
|
- customer
|
|
- support
|
|
scheme: http
|
|
host: ${REST_HOSTNAME}
|
|
responses:
|
|
'200':
|
|
content:
|
|
application/json:
|
|
schema:
|
|
type: object
|
|
description: Customer payment records
|
|
properties:
|
|
id:
|
|
type: integer
|
|
readOnly: true
|
|
checknumber:
|
|
type: string
|
|
maxLength: 50
|
|
paymentdate:
|
|
type: string
|
|
format: date
|
|
amount:
|
|
type: string
|
|
format: decimal
|
|
pattern: ^-?\d{0,8}(?:\.\d{0,2})?$
|
|
customernumber:
|
|
type: integer
|
|
maximum: 2147483647
|
|
minimum: -2147483648
|
|
required:
|
|
- amount
|
|
- checknumber
|
|
- customernumber
|
|
- id
|
|
- paymentdate
|
|
- annotations:
|
|
title: Create a new payment
|
|
read_only_hint: false
|
|
idempotent_hint: false
|
|
destructive_hint: false
|
|
open_world_hint: false
|
|
description: Record a new customer payment with check number, amount, and payment date.
|
|
method: POST
|
|
name: create-payment
|
|
path: /payments/v1/payments/
|
|
request_body:
|
|
content:
|
|
application/json:
|
|
schema:
|
|
properties:
|
|
amount:
|
|
type: string
|
|
checknumber:
|
|
type: string
|
|
customernumber:
|
|
type: integer
|
|
paymentdate:
|
|
type: string
|
|
required:
|
|
- amount
|
|
- checknumber
|
|
- customernumber
|
|
- paymentdate
|
|
type: object
|
|
required: true
|
|
acl:
|
|
allow:
|
|
- admin
|
|
scheme: http
|
|
host: ${REST_HOSTNAME}
|
|
responses:
|
|
'201':
|
|
content:
|
|
application/json:
|
|
schema:
|
|
type: object
|
|
description: Customer payment records
|
|
properties:
|
|
id:
|
|
type: integer
|
|
readOnly: true
|
|
checknumber:
|
|
type: string
|
|
maxLength: 50
|
|
paymentdate:
|
|
type: string
|
|
format: date
|
|
amount:
|
|
type: string
|
|
format: decimal
|
|
pattern: ^-?\d{0,8}(?:\.\d{0,2})?$
|
|
customernumber:
|
|
type: integer
|
|
maximum: 2147483647
|
|
minimum: -2147483648
|
|
required:
|
|
- amount
|
|
- checknumber
|
|
- customernumber
|
|
- id
|
|
- paymentdate
|