Skip to main content
Glama

奇妙生产力 · Qimiao Productivity

quote_order

免费冻结输入、模板和材料hash,返回服务单与私人凭证。先prepare_task,带draft凭据和固定随机request_key实现安全重试;需求完整时requirements_confirmed=true,只问缺失信息。客户端无法编辑自由Object时改用input_json(JSON对象字符串),与input二选一。向用户确认价格/交付后再购买。

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": {
      "tool_id": "<tool_id>",
      "request_key": "<request_key>"
    },
    "name": "quote_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputNo
tool_idYes
draft_idNo
input_jsonNo客户端无法编辑自由Object时使用:按get_tool的input.schema填写JSON对象字符串。与input二选一,不能同时传入。
request_keyYes
draft_credentialNo

Output Schema

NameRequiredDescriptionDefault
recoveryYes
next_stepYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / input_json
      Added value: +{
      +  "description": "客户端无法编辑自由Object时使用:按get_tool的input.schema填写JSON对象字符串。与input二选一,不能同时传入。",
      +  "maxLength": 64000,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "tool_id",
      -  "input",
      -  "request_key"
      -]New value: +[
      +  "tool_id",
      +  "request_key"
      +]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Adds real value beyond annotations by saying the call is free and returns a private credential, and by explaining the retry mechanism (same request_key). However, the fixed-request_key retry story sits in tension with idempotentHint=false and is not reconciled, and no error/permission behaviour is described.

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 outcome (freeze + return order/credential), then prerequisites, then the purchase warning. Dense but nearly every clause adds operational information; the 'requirements_confirmed=true' instruction is the one clause that does not map cleanly to any parameter.

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 6-parameter, open-world mutation tool with an output schema (so return values need not be explained), the description covers prerequisites, credential handling, input-mode selection and the purchase gate. Missing only tool_id/draft_id semantics and failure behaviour.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 17%, so the description carries most of the burden, and it does: it explains input vs input_json as mutually exclusive alternatives, the purpose of draft_credential, and the request_key retry contract. tool_id and draft_id are still undocumented, which keeps it off a 5.

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+resource: freezes input/template/material hash and returns a service order plus private credential ('冻结输入、模板和材料hash,返回服务单与私人凭证'). That distinguishes it from create_order/pay_with_balance implicitly (it is the free quoting step), though it never names the sibling it differs from.

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

Usage Guidelines5/5

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

Explicit sequencing: call prepare_task first and pass the draft credential; use a fixed random request_key for safe retry; confirm price/delivery with the user before purchasing. That is a concrete when-to-use, prerequisite, and pre-condition for a later tool, not just context.

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