Skip to main content
Glama

Get operation schema

get_endpoint_details_full
Read-onlyIdempotent

Get COMPLETE schema and details for a specific API operation.

Use this BEFORE calling an API to understand exactly what parameters are needed.

Args: operationId: The operation ID (e.g., "syncQuickContactReveal")

Returns: Complete schema including all required/optional fields, request body schema, response schema, and example usage.

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": {
      "operationId": "<operationId>"
    },
    "name": "get_endpoint_details_full"
  }
}

Input Schema

NameRequiredDescriptionDefault
operationIdYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered without the description. The description adds the structure of what comes back (required/optional fields, request body, response schema, example usage), which is useful but largely duplicated by the existing output schema; no auth, rate-limit, or failure behavior is disclosed.

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?

Front-loaded with the purpose, then a usage directive, then structured Args/Returns sections with no filler. The Returns block restates information an output schema already supplies, which is minor waste but not harmful.

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?

For a one-parameter read-only lookup with an output schema and full annotation coverage, nothing essential is missing: purpose, timing, parameter format, and return shape are all addressed. The only soft gap, provenance of the operationId, is a nice-to-have rather than a blocker.

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

Parameters3/5

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

Schema coverage is 0% for the single operationId parameter, so the description must carry the burden. It does add a concrete format example ('syncQuickContactReveal'), which is genuine value, but omits the key semantic question of how an agent obtains an operationId (presumably via list_all_endpoints or search_endpoints).

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

Purpose4/5

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

States a specific verb and resource ('Get COMPLETE schema and details for a specific API operation'), which is clearly distinguishable from list_all_endpoints and search_endpoints. It does not explicitly name the sibling it pairs with (call_operation), but the 'before calling an API' phrasing makes the relationship inferable.

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?

Gives explicit timing guidance: 'Use this BEFORE calling an API to understand exactly what parameters are needed,' which frames the tool as a prerequisite to invocation. It stops short of naming the alternative (call_operation) or stating when-not to use it, e.g., when the schema is already known.

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