Skip to main content
Glama
Nevery-qiao

qianji-agent

by Nevery-qiao

qianji_connection

Read-onlyIdempotent

Verify whether the official macOS bookkeeping app's login state can be read in the background; no account or login details are returned.

Instructions

核对官方App登录态能否后台读取;不返回账号或登录信息。

Input Schema

NameRequiredDescriptionDefault

No arguments

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld behavior. The description adds one useful constraint—no account/login information is returned—but does not cover auth needs, latency, rate limits, or result interpretation. With annotations covering safety, this is a modest addition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with a semicolon separating purpose from output constraint. No wasted words.

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

Completeness5/5

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

Given the simple no-parameter operation, rich annotations, and an output schema, the description is complete enough: it states what is checked and what is not returned. No additional behavioral or return details are required from the description.

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?

The tool has zero parameters, so the baseline is 4. The description adds no parameter information because none exist.

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 check: verifying whether the official App login state can be read in the background, and clarifies that no account or login data is returned. It is clear but does not name a sibling tool, so sibling differentiation is only implicit via the privacy note.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like qianji_account_review or qianji_query. The diagnostic purpose is implied but there is no instruction about prerequisites or when-not-to-call.

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