Skip to main content
Glama

order.detail

order_detail

[需要登录] 查询单个订单完整详情,包括预约信息、医院信息、套餐项目、支付状态。

鉴权:需要用户登录令牌,或已经绑定用户的云市场实例凭证。未登录调用返回 401;云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

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": {
      "serviceid": "<serviceid>"
    },
    "name": "order_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does so well: it declares the auth requirement (user login token or user-bound cloud marketplace credentials) and the exact failure behaviors — 401 when unauthenticated, code=40003 plus data.bindUrl when the marketplace instance has no bound user. It does not mention rate limits or ordering of checks, but the preconditions an agent must satisfy are clear.

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?

Front-loaded with the login requirement, then purpose, then a separate 鉴权 block. Every sentence carries information; the error-code detail is dense but earns its place since no annotations exist.

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?

There is no output schema, and the description usefully lists the returned sections and the two auth failure modes, which is good coverage. The remaining gap is the required 'serviceid' argument, which is undocumented in both schema and description, so an agent knows what it gets back but not how to ask for it.

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% and the single required parameter 'serviceid' is never explained — not whether it is an order identifier, a service identifier, nor its format. This is exactly the case where the description must compensate, and it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('查询单个订单完整详情') and enumerates the content returned (预约信息、医院信息、套餐项目、支付状态). The word '单个' (single) implicitly contrasts with the sibling order_list, so an agent can distinguish list vs. detail without opening a schema.

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?

Usage is implied by 'single order detail' and the login precondition, but the description never states when NOT to use it or names order_list as the alternative for multi-order lookups. Adequate but leaves the routing decision to inference.

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