Get endpoint details
get_endpointFull contract of one endpoint: method, URL, auth, query and header parameters, request body example, example responses (large bodies truncated, full text on the docs page). Accepts the endpoint id from search/list, or 'METHOD /path'. Path parameters may use any name or spelling (':cart', '{cartId}', a concrete value); a leading '/api' or '/v1' is ignored. Some routes are recorded several times with different query parameters: a reference without query string resolves to the recording without query parameters, a reference with a query string (e.g. '?$expand=All') to the recording with exactly (or at least) those keys. If that still leaves several recordings, the result is { ambiguous: true, candidates: [{ id, name, method, path }] } instead of the contract — call again with one of the candidate ids. When nothing matches, the error lists the nearest endpoints of that method.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"endpoint": "<endpoint>"
},
"name": "get_endpoint"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| endpoint | Yes | Endpoint id (e.g. 'ticket-purchase-registration/cart/create-cart') or 'POST /api/shop/cart' |