Skip to main content
Glama

奇妙生产力 · Qimiao Productivity

respond_to_run

Idempotent

回答持久化交付问题,版本和请求编号固定;答复后后台继续执行。歌曲改编的lyrics_review须先让用户确认完整歌词,再把{lyrics_confirmed:true,lyrics:完整歌词}作为answer的JSON字符串,沿用原服务单,不另购。

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": {
      "service_id": "<service_id>",
      "credential": "<credential>",
      "interaction_id": "<interaction_id>",
      "version": "<version>",
      "answer": "<answer>",
      "request_key": "<request_key>"
    },
    "name": "respond_to_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerYes
versionYes
credentialYes
service_idYes
request_keyYes
interaction_idYes

Output Schema

NameRequiredDescriptionDefault
recoveryYes
next_stepYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / answer / maxLength
      Previous value: -2000New value: +16000
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only but idempotent operation; the description adds the important trait that execution continues in the background after the answer is submitted, and that version and request_key are fixed for the lifetime of the interaction. The lyrics-confirmation flow and no-extra-purchase rule add further behavior an agent could not infer from annotations. It does not discuss auth or failure modes, keeping it short of a 5.

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 dense sentences with no filler, and the core action plus its post-answer behavior are front-loaded before the lyrics special case. The high density and mixed Chinese/English jargon make it slightly harder to parse but nothing is wasted.

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?

An output schema exists, so return values need not be described. Still, with six required parameters at 0% schema coverage and a mutation-like tool, the description leaves credential and interaction_id unexplained and gives no guidance on what happens on version conflicts or duplicate request keys.

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 0%, so the description must carry the burden. It explains that version and request_key are fixed and specifies the exact answer payload shape for lyrics_review (a JSON string with lyrics_confirmed and lyrics), and references reusing the original service order. It says nothing about credential validity, interaction_id format, or why six fields are all required, so compensation is partial.

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: it answers a persisted delivery question ('回答持久化交付问题') and notes that the backend keeps executing afterwards. This distinguishes it from read-only siblings like get_run_result and get_run_events, though the wording is terse and assumes domain familiarity with 'delivery question'.

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?

It gives explicit preconditions for one scenario — for song-adaptation lyrics_review the user must first confirm the complete lyrics, and the original service order is reused without a new purchase. However, there is no general when-to-use/when-not guidance and no mention of alternatives such as get_run_result or request_change.

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