yimu-mcp

sync_pull

sync_pull

Incrementally pulls bookkeeping data updated since a given timestamp. Returns a compact summary by default for quick AI analysis, or full entity details when requested.

Instructions

增量拉取业务数据（GET /updateTime/getUpdateDataPage/{userId}/{time}）。默认返回摘要：syncTime、各实体计数、收支合计、最近10笔、分类Top10、资产列表——适合 AI 快速分析账目；需要完整明细时传 summary=false，各实体按业务字段精简返回（Bill 只含 billId/cost/日期/分类/备注等）。time 为上次同步时间戳(ms)，缺省 0 表示全量。

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": "sync_pull"
  }
}

Input Schema

Name	Required	Description
`time`	No	上次同步时间戳(ms)，0=全量
`summary`	No	默认 true：返回摘要；false 返回全部实体明细（已精简）
`user_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.0Oct 29, 2026

addedInput schema / properties / summary

Added value: +{
+  "description": "默认 true：返回摘要；false 返回全部实体明细（已精简）",
+  "type": "boolean"
+}

First observedv0.1.2Sep 15, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the default return shape (syncTime, per-entity counts, income/expense totals, last 10 records, category Top10, asset list) and what changes when summary=false. Gaps remain: no mention of auth/user_id requirements, whether the call mutates server sync state (relevant given sibling sync_start/sync_end), or error 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?

Front-loads the operation and endpoint, then the default behavior, then the override mode. Dense but efficient; the only waste is the restatement of the time parameter semantics already present in the schema.

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?

No output schema and no annotations, so the description must cover the return contract — and it largely does. However, the undocumented user_id parameter and the unstated relationship to sync_start/sync_end leave real gaps for an agent deciding how to call this correctly.

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 67% — time and summary are already documented in the schema and the description largely restates them. It does add value by explaining what summary=false actually returns per entity (Bill reduced to billId/cost/date/category/remark), but user_id is undocumented in both schema and description.

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 (incremental pull of business data since a timestamp) and even names the underlying endpoint. It does not explicitly contrast itself with siblings such as get_book_bills or sync_start/sync_end, but the described payload makes the distinction inferable.

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?

Gives clear mode-selection guidance: default summary is for fast AI analysis of accounts, and summary=false should be used when full detail is needed. It does not say when NOT to use this tool or name an alternative sibling, which keeps it below a 5.

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