Skip to main content
Glama
qianji-agent

qianji-agent

by Nevery-qiao

qianji_recovery_scheduler

Idempotent

Reads scheduling intent or registers the host's canonical read-back for recovery checks, without creating/canceling tasks or sending financial requests.

Instructions

读取唯一调度意图或登记宿主正规回读;此工具不直接创建/取消宿主任务,也不发送金融请求。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "qianji_recovery_scheduler"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNostatus
observationNo

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.1/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description adds real scope context by clarifying it never creates/cancels host tasks or sends financial requests. It still leaves unexplained what the 'record' mutation actually does or what authorization/side effects it carries, which matters since readOnlyHint=false.

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?

A single dense sentence with the two capabilities front-loaded and the negative scope trailing, with no filler. It is compact, though its abstract vocabulary makes it slightly harder to parse than plain wording would be.

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

Completeness2/5

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

An output schema exists and annotations cover the safety profile, so return values and safety need not be restated. But for a tool whose 'record' path writes an observation object, the description omits the semantics of both the action and the observation payload, leaving a meaningful gap.

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%, so the description must carry parameter meaning. It loosely gestures at the two actions but never explains the 'action' enum values, and it says nothing about the nested observation fields (expected_generation, mode, observed_state, observation_reference), leaving the write path opaque.

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 names two concrete capabilities (read the scheduling intent, register host readback) that map onto the action enum, and it delineates the tool from task-mutating siblings by stating it does not create/cancel host tasks. The resource labels are somewhat abstract ('唯一调度意图', '宿主正规回读'), but an agent can tell it is a read/registration tool and not the create/cancel one.

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 a useful 'when-not' boundary (does not create/cancel host tasks, does not send financial requests), which steers the agent away from misuse. However, it never names which sibling to use instead (e.g. qianji_recovery_list vs qianji_recovery_ack) or states the condition that selects status vs record.

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