Skip to main content
Glama

Get endpoint

get_endpoint
Read-onlyIdempotent

Full detail of one endpoint: parameters, params and response JSON Schemas, an example, price, limits, stats and health. Free, and works without an API key.

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
endpointYesThe endpoint slug (e.g. "agents-risk"), its path (e.g. "/agents/risk") or "GET /agents/risk"

Output Schema

NameRequiredDescriptionDefault
nameYes
pathYes
slugYes
priceYes
healthYes
methodYes
paramsYes
descriptionYes
params_schemaYes
response_schemaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 safety and idempotency are covered. The description contributes the notable operational fact that the call is free and requires no API key, plus a preview of returned content, but adds nothing about failure modes for invalid slugs or response size.

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?

One compact sentence, front-loaded with the core action, and the itemized field list is dense rather than padded. The cost/auth clause is appended where it is useful without burying the main statement.

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

Completeness4/5

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

With an output schema present, return-shape explanation is optional, yet the description still summarizes payload contents, and it notes the no-key access model. For a single-parameter read tool with annotations, the only real omission is comparative guidance against sibling tools.

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 description coverage is 100% and the single parameter's description already gives concrete formats (slug, path, or "GET /path") with an example. The description adds no format or normalization guidance beyond what the schema supplies, so the baseline 3 applies.

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 ("Full detail of one endpoint") and enumerates exactly what the detail includes: schemas, example, price, limits, stats, health. An agent can distinguish this from a call/execute tool by the word "detail", though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives such as call_endpoint or search_endpoints, and no exclusions. The only contextual note is "Free, and works without an API key," which describes access conditions rather than selection guidance.

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