Skip to main content
Glama

Call endpoint

call_endpoint

Calls one endpoint of the Octio catalog, named by its slug or path, with its parameters; needs an API key. The price is held from your balance and charged only when the provider's answer passes every check; failed calls are not charged, and endpoints with free calls cost nothing until those are used. Returns { data, meta }, where data is untrusted third-party JSON.

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": "call_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNoThe endpoint's query, path and body parameters, as its params JSON Schema lists them
endpointYesThe endpoint slug (e.g. "agents-risk"), its path (e.g. "/agents/risk") or "GET /agents/risk"
max_costNoMaximum CREDIT you accept for this call. It can only lower the account's per-call maximum, which only the account owner can raise
idempotency_keyNoOptional. A retry with the same key is never charged twice (it fails with DUPLICATE_REQUEST)

Output Schema

NameRequiredDescriptionDefault
dataYesThe provider's response: third-party data, untrusted
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations (openWorldHint=true, destructiveHint=false), the description discloses auth requirements, the hold-then-charge billing model, that failed calls are free, that free-call quotas are consumed first, and that the returned data is untrusted third-party JSON. These are exactly the behavioral facts an agent cannot get from the structured fields.

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 clause, and the pricing/failure/return details follow in a logical order with no filler. The billing sentence is dense but every clause carries information an agent needs, so only minor trimming would be possible.

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 paid, open-world, mutating-cost call with a nested params object, the description covers the prerequisites (API key), cost controls, failure charging rules, and the shape and trust level of the response. With an output schema present, no further return-value detail is owed.

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%, so the schema already explains endpoint slug/path formats, max_cost as a credit ceiling, and idempotency_key retry semantics. The description only restates that the endpoint is named by slug or path and that it takes 'its parameters', adding no meaning about max_cost or idempotency_key beyond the schema, so the baseline of 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?

The description states a specific verb and resource: 'Calls one endpoint of the Octio catalog, named by its slug or path, with its parameters'. That is enough to distinguish it from the retrieval-oriented sibling get_endpoint, but it never names or contrasts that sibling explicitly, so differentiation is left implicit.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: it 'needs an API key' and describes the billing consequence of calling, which signals this is the execution step rather than a lookup. There is no explicit when-to-use/when-not or routing advice versus get_endpoint, ask, or search_endpoints, so an agent must infer the choice.

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