Skip to main content
Glama

面灵AI 面试助手

check_order_status

Read-only

查询一笔订单是否已付款到账。用户在收银台付款后用它确认;状态为 PAID 即已到账。(需要用户授权,范围 account:read)

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": {
      "orderNumber": "<orderNumber>"
    },
    "name": "check_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNumberYes下单工具返回的订单号,或 get_account 最近订单中的订单号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds a real behavioral fact beyond them: the call requires user authorization with scope account:read, and PAID is the terminal success value. It still says nothing about pending/failed states or the response shape.

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?

Three compact clauses: what it does, when to call it, how to interpret the result, with the auth prerequisite parenthesized at the end. Nothing is redundant, though the auth note could be front-loaded since it gates the call.

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

Completeness4/5

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

For a single-parameter read-only lookup with no output schema, the definition covers purpose, trigger, the meaning of the key return value, and the authorization prerequisite. Only the non-success status values are left implicit.

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 coverage is 100% and the schema already tells the agent that orderNumber comes from the ordering tool or get_account recent orders; the description adds no format or validation detail beyond that, so the 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?

The description states a specific verb and resource: query whether a single order has been paid. The sibling create_payment_order is implicitly contrasted (query vs. create) and the PAID semantics make the intent unambiguous, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

It gives a clear usage context — call it after the user pays at checkout to confirm the funds arrived — which is exactly the moment an agent needs it. It does not state when not to use it or what to do if the status is not PAID, but the positive guidance is concrete.

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