yimu-mcp

get_book_last_time

get_book_last_time

Retrieve the last sync timestamp for a ledger to use as an incremental sync cursor, enabling efficient data synchronization.

Instructions

查询账本最后同步时间戳(ms)（GET /bill/getAccountLastTime/{userId}/{bookId}），可作增量同步游标。

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": {
      "book_id": "<book_id>"
    },
    "name": "get_book_last_time"
  }
}

Input Schema

Name	Required	Description	Default
`book_id`	Yes	账本 ID
`user_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 15, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the HTTP GET method and the millisecond timestamp result, implying a non-mutating read. However, it does not mention authentication requirements, behavior for a never-synced book, or explicit no-side-effect guarantees.

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?

The description is a single dense sentence that front-loads the core purpose, endpoint, timestamp unit, and usage intent. There is no filler or redundant content.

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?

For a simple two-parameter read tool with no annotations and no output schema, the description is mostly adequate: it states what is returned and why it is useful. However, it is incomplete about the optional user_id semantics and edge cases, which an agent may need to handle correctly.

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 only 50%: book_id is documented but user_id is not. The description adds only the endpoint path hint showing both userId and bookId, but it does not clarify why user_id is optional or what it represents in the query. This leaves a meaningful gap for an agent trying to invoke the tool correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific read operation ('查询账本最后同步时间戳'), identifies the resource (the account book), gives the endpoint, and explains its purpose as an incremental sync cursor. This clearly distinguishes it from sibling sync-related tools like sync_pull or sync_start.

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?

The description clearly indicates when to use the tool: to obtain the last sync timestamp for use as an incremental sync cursor. It does not explicitly name alternatives or state when not to use it, but the cursor hint provides enough context for an agent to route correctly.

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