yimu-mcp

save_bills

save_bills

Batch add or update multiple bookkeeping bills in one request, auto-splitting into 100-item chunks with incremental update times.

Instructions

批量新增/更新账单（POST /bill/addOrUpdateBillList）。自动按 100 条分批、每批 updateTime 递增（与网页端一致）。bill 字段同 save_bill。

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": {
      "bills": "<bills>"
    },
    "name": "save_bills"
  }
}

Input Schema

Name	Required	Description	Default
`bills`	Yes	账单对象数组（自动分批）

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 15, 2026

TDQS

A4.1/5.0

Behavior3/5

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

在没有任何注解的情况下，描述主动披露了自动分批、每批 updateTime 递增、与网页端一致等超出 schema 的行为，这对批量写入工具很有价值。但它未说明鉴权要求、返回内容、部分批次失败后的行为或整体原子性，对于写入类工具仍有明显缺口。

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?

两句话内依次交代了动作、端点、分批行为、updateTime 语义和字段参照，信息密度高，没有冗余或装饰性内容，结构紧凑且关键信息前置。

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?

描述覆盖了核心调用信息：端点、批量语义、批次大小、时间戳策略和字段来源，足以支撑基本调用。但没有输出 schema、也没有说明返回值或失败处理方式，对批量写操作而言还称不上完全自足。

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?

输入 schema 中 bills 参数只是泛化的对象数组，字段结构依赖描述中的“bill 字段同 save_bill”补全，这为调用者提供了比 schema 更具体的参数含义。虽然需要查阅 save_bill 才能获得完整字段列表，但已有明确指引，价值高于单纯重复 schema 描述。

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?

描述以明确的动词和资源开头：“批量新增/更新账单”，并附带具体端点 POST /bill/addOrUpdateBillList。通过“bill 字段同 save_bill”与单条保存工具形成区分，使工具的功能边界清晰，不会与 save_bill 等兄弟工具混淆。

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?

“批量”和“自动按 100 条分批”清晰传达了该工具适用于多条账单提交场景，并借用 save_bill 提示字段一致性。虽然没有显式写出“单条请用 save_bill”这样的排除条件，但使用场景已经足够清楚。

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