yimu-mcp

get_bill_count

get_bill_count

Retrieves the total number of bills recorded for a specified user ID. Use it to quickly determine how many bills exist in a Yimu bookkeeping ledger.

Instructions

查询账单总数（GET /bill/getBillCount/{userId}）。

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

Input Schema

Name	Required	Description	Default
`user_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 15, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It mentions 'GET' and '查询', which weakly imply a read-only operation, but it does not disclose authentication needs, possible failure modes, response format, or any 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 compact sentence that front-loads the purpose and includes the endpoint. There is no redundant or wasted text.

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?

For a simple one-parameter GET tool, the description is minimally adequate, but with no annotations, no output schema, and no usage guidance, it lacks important context such as return value, authentication expectations, and when to use it versus similar bill tools. More detail would meaningfully improve the definition.

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?

The input schema has no description for user_id and schema coverage is 0%. The description's endpoint template {userId} hints that the parameter is a path parameter, but it does not clarify requiredness, expected format, or what value should be supplied.

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 clearly states a specific action ('查询' / query) and resource ('账单总数' / total bill count), and provides the exact HTTP endpoint. It is not a tautology, but it does not explicitly differentiate itself from sibling bill-related tools such as get_book_bills.

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?

The description provides no guidance on when to use this tool versus alternatives, no mention of prerequisites or exclusions, and no context about suitable scenarios. An agent must infer usage solely from the name and endpoint.

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