Skip to main content
Glama

threads-instagram-truthsocial-linkedin-posts-mcp

call_endpoint

Execute an endpoint and return compact LLM-ready output (-80% context tokens).

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_id": "<endpoint_id>"
    },
    "name": "call_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNocompact
paramsNo
endpoint_idYes
max_cost_usdNoPer-call USD ceiling

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=false, so the description must explain the consequences of execution: external network calls, potential side effects or charges, and failure modes. It discloses none of these, mentioning only that output is compacted for token savings, which is an output-shape claim rather than behavioral context.

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?

A single front-loaded sentence with no filler; the token-reduction clause is a value claim but is at least relevant to callers optimizing context. Nothing is buried or redundant.

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?

For a tool that executes arbitrary remote endpoints with a nested params object and no output schema, the description omits execution semantics, cost behavior, and error handling. It is adequate only as a one-line identity, not as enough context to invoke the tool safely.

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 only 25% (just max_cost_usd), and the description adds no meaning to endpoint_id, format, or the free-form nested params object. With a nested open-ended params bag and an undocumented format enum, the description leaves parameter semantics entirely to the schema.

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 ('Execute an endpoint') and adds an outcome claim about compact LLM-ready output. It does not differentiate itself from siblings like get_endpoint_schema or search_endpoints, though their names imply clearly different operations.

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?

No guidance on when to call this versus other tools, no prerequisites (auth, endpoint readiness), and no conditions under which execution should be avoided. The only usage cue is the implied token-saving benefit.

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