Skip to main content
Glama

调用接口 / Call an endpoint

call
Read-only

调用一个接口取数据,成功才扣费,返回里写明扣了多少。Call an endpoint; charged only on success, and the answer says what it cost.

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

Input Schema

NameRequiredDescriptionDefault
paramsNo接口参数,见 describe。翻页时传 cursor / Parameters, see describe; pass cursor for the next page
endpointYes接口 ID
max_priceNo这次最多愿意付多少美元,超过就不调用,例如 "0.01" / Refuse the call if it costs more than this (USD)
idempotency_keyNo重试同一次调用时传同一个值,不会重复扣费 / Same value on a retry is never charged twice

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only say readOnlyHint and openWorldHint; the description adds the materially important commercial behaviour — you are charged only on success and the response reports the amount charged. That is genuine value beyond annotations. It stops short of describing failure modes or what an error response looks like.

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?

Two short clauses, front-loaded with purpose followed by the billing guarantee, with no filler. The Chinese/English duplication roughly doubles the length, which is the only wasted space.

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?

With no output schema, the description carries some of the return burden and does cover cost reporting, but it says nothing about the shape of the returned data or how errors are surfaced. For an open-world generic caller, that leaves a noticeable gap.

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 all four parameters already carry their own explanatory text, which sets the baseline at 3. The description adds no parameter-level meaning beyond the 'see describe' pointer for the params object.

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 an endpoint') and points at 'describe' for parameter discovery, which implicitly separates it from the catalog-lookup siblings. It stays generic about what an 'endpoint' is and never distinguishes itself from 'find' or 'account', so an agent still has to infer the boundary.

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?

There is an implied ordering signal in '接口参数,见 describe', telling the agent to look up params before calling, and the cursor note covers pagination. But there is no explicit statement of when to use this versus describe/find/account, and no prerequisites or failure-handling 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