Skip to main content
Glama
qianji-agent

qianji-agent

by Nevery-qiao

qianji_recovery_ack

Idempotent

Mark a recovery item closed after the original outcome is verified: record the caller's disposition and completion reference, changing only recovery metadata; unknown outcomes cannot be closed.

Instructions

原结果已查明且调用方接续台账/处置后确认收尾;未知不能关闭。只改恢复元数据。

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": {
      "request_id": "<request_id>",
      "expected_version": "<expected_version>",
      "disposition": "<disposition>",
      "completion_reference": "<completion_reference>"
    },
    "name": "qianji_recovery_ack"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes
dispositionYes
expected_versionYes
completion_referenceYes

Output Schema

NameRequiredDescriptionDefault
codeNo
stateYes
totalNo
actionNo
deletedNo
recordsNo
recoveryNo
trackingNo
image_keyNo
object_idNo
book_countNo
compatibleNo
operationsNo
request_idNo
limitationsNo
next_offsetNo
writes_sentNo
capabilitiesNo
continuationNo
account_reviewNo
backup_createdNo
dispatch_stateNo原财务发送留证状态;不是成功/无效果证明,不允许据此重发
safe_to_resendNo
complete_sourceNo
runtime_versionNo
download_variantNonative_huge为官方账单图片域名的!huge显示版本;服务可能重新编码
related_bill_idsNo
requires_versionNo
balances_verifiedNo
expected_balancesNo
verification_codeNo有限的核验失败类别;旧请求缺失发送证据不会自动解除未知屏障
dispatch_error_codeNo
file_content_verifiedNo
image_pixels_verifiedNo严格HTTPS下载原生无损显示版本,与本地原图按方向归一化后逐像素相同;不等于原文件字节相同
storage_hash_verifiedNo
native_fields_verifiedNo
task_execution_observedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare idempotent=true, destructive=false, readOnly=false. The description adds useful scope context that mutation only touches recovery metadata and that unknown-state cases cannot be closed, but it does not explain expected_version semantics (optimistic concurrency), permission requirements, or failure behavior.

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?

Short and front-loaded: the precondition leads and the scope constraint closes. Every clause carries meaning, though the terse, semicolon-chained phrasing is somewhat cryptic for a reader unfamiliar with the domain.

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, and the preconditions are covered. However, for a 4-parameter mutation with 0% schema coverage, the absence of any parameter-level explanation leaves the definition only minimally adequate.

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 coverage is 0% across 4 required parameters (request_id, expected_version, disposition, completion_reference) with no schema descriptions. The description loosely gestures at '处置' (disposition) but does not explain any parameter's meaning, format, or the enum values, so it fails to compensate for the coverage gap.

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 conveys a specific action ('确认收尾' – confirm closure of the recovery case) conditioned on the original result being verified, and scopes the effect ('只改恢复元数据'). It is more than a restatement of the name, though the verb is implied rather than stated outright, so a 4 rather than a 5.

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 explicit preconditions for use (result already investigated, caller has continued the ledger/disposition) and an explicit exclusion ('未知不能关闭' – unknown state cannot be closed). It stops short of naming sibling alternatives such as qianji_recovery_list or qianji_recovery_scheduler, so it does not reach 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.