Skip to main content
Glama

ADITUS Developer Portal MCP

Get endpoint details

get_endpoint
Read-onlyIdempotent

Full 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

NameRequiredDescriptionDefault
endpointYesEndpoint id (e.g. 'ticket-purchase-registration/cart/create-cart') or 'POST /api/shop/cart'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well past the readOnly/idempotent annotations: discloses that large response bodies are truncated with full text only on the docs page, documents the exact shape of the ambiguity result ({ ambiguous: true, candidates: [...] }) and the follow-up action, and describes the error behavior (nearest endpoints of that method). This is unusually rich disclosure for a read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence and every subsequent clause carries resolution semantics, not filler. The query-string disambiguation paragraph is dense and slightly hard to parse on first read, but nothing is expendable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so: contract contents, truncation caveat, the alternative ambiguity payload, and error fallback. An agent has everything needed to call this correctly and to recover from both ambiguous and empty results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, yet the description adds substantial meaning: id vs 'METHOD /path' reference forms, tolerance for any path-parameter spelling or concrete values, ignoring of leading '/api' or '/v1', and query-string-based recording disambiguation. This is well beyond what the one-line schema field conveys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Full contract of one endpoint') and enumerates exactly what the contract contains: method, URL, auth, query/header params, body and response examples. It also names the upstream source of the identifier ('from search/list'), so the agent can place it relative to list_endpoints/search_docs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Makes clear this is the follow-up call once an endpoint id is known from search/list, and gives explicit rules for the reference forms it accepts. It lacks an explicit 'use get_guide/search_docs instead for X' exclusion, but the retrieval workflow is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources