Skip to main content
Glama

BRAINIAC API catalog

Call endpoint

call_endpoint

Call one paid POST endpoint by id. Unpaid calls return 402 and do not run. Payment settles only after a successful result.

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": {
      "id": "<id>"
    },
    "name": "call_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
paramsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful traits: paid-only execution, the 402 failure mode with no side effect, and billing settling only on success. However, for a cost-bearing tool it omits the highest-risk behavior — whether retries double-charge, idempotency, auth requirements, and what a successful response contains — leaving material gaps.

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

Conciseness5/5

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

Three short sentences with zero filler, and the most decision-relevant facts (paid only, 402 on unpaid, settlement timing) are front-loaded. Every sentence earns its place.

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

Completeness3/5

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

It covers cost and the failure path well, but a tool that executes arbitrary POST payloads against a paid endpoint, with a nested params object, no output schema, and no annotations, needs to describe the payload contract and the shape of a result. Those omissions matter given the tool's complexity and financial risk.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and it largely does not. 'By id' clarifies the id parameter as an endpoint identifier, but the nested `params` object — the actual request payload — is never explained at all, leaving the most complex parameter undocumented in both schema and description.

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: 'Call one paid POST endpoint by id.' That clearly separates it from the read-oriented siblings (describe_endpoint, list_apis, search_endpoints), which cannot execute anything. It stops short of a 5 only because it does not explicitly contrast itself with those siblings.

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?

It supplies one real precondition — the endpoint must be paid, otherwise the call returns 402 and does not execute — which is a genuine when-it-works rule. But there is no guidance on ordering (e.g., resolve the id via search_endpoints/describe_endpoint first) and no statement of when not to use it, such as read-only or idempotency-sensitive situations.

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