Skip to main content
Glama

call_model

通过本站网关调用指定模型(OpenAI 兼容接口)。必须提供用户自己的网关令牌 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": {
      "model": "<model>",
      "prompt": "<prompt>",
      "api_key": "<api_key>"
    },
    "name": "call_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes模型标识,如 claude-sonnet-5-5
promptYes用户提示词
systemNo可选,系统提示词
api_keyYes本站令牌(sk- 开头),仅用于本次请求
max_tokensNo可选,最大输出 token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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. It usefully discloses the auth model (user-supplied key, server does not persist it), which is real behavioral context. However it says nothing about latency, rate limits, billing, streaming, or error behavior for what is a live model invocation.

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 sentences, front-loaded with the action and immediately followed by the critical auth constraint. No filler, though the parenthetical interface note could be folded in more tightly.

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 five-parameter tool with no annotations and no output schema, the description covers the call mechanism and auth but never indicates what comes back (an OpenAI-compatible completion object) or how failures surface. That leaves a meaningful gap for an agent that must consume the result.

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 five parameters are already documented in the schema, including that api_key is an sk- token used only for this request. The description adds only the marginal fact that the server does not store the key, so 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 ('调用指定模型') plus the mechanism ('通过本站网关', 'OpenAI 兼容接口'), which lets an agent distinguish it from list_models/compare_models as the tool that actually executes a call. It stops short of explicitly naming those siblings as alternatives.

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?

The description establishes a hard precondition (the caller must supply their own gateway api_key) but gives no guidance on when to choose this over compare_models or list_models, nor on model selection or cost implications. Usage is only implied by the tool's nature.

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.