Sivella

Spending by category

get_category_breakdown

Read-only

Debit entries for one category in one ledger-month (amounts in currency units, not cents).

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": {
      "ledger_id": "<ledger_id>",
      "month": "<month>",
      "category_slug": "<category_slug>"
    },
    "name": "get_category_breakdown"
  }
}

Input Schema

Name	Required	Description
`month`	Yes	Calendar month YYYY-MM. For a year-less month, use the most recent occurrence on or before the current month.
`ledger_id`	Yes
`category_slug`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavior beyond them by specifying debit entries only and clarifying that amounts are in currency units, not cents, but it omits ordering, pagination, and aggregation behavior.

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 front-loaded sentence. The parenthetical currency-unit clarification earns its place by preventing a likely unit error, and there is no filler.

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 small read-only query, the description states the scope and the unit, which is adequate but incomplete. With no output schema, it does not fully describe whether results are raw entries, totals, or grouped data, and it leaves two required parameters undocumented.

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 33%, with month being the only documented parameter. The description refers to 'one category' and 'one ledger-month' but never explains ledger_id or category_slug meaning or format, so it does not compensate for the low schema coverage.

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 output and scope: debit entries for one category in one ledger-month, plus the amount unit. It is clear what the tool returns, but it does not distinguish itself from siblings such as list_budget_categories or get_ledger_summary.

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 implies a retrieval use case but provides no explicit when-to-use or when-not-to-use guidance. It names no alternatives or conditions for choosing this tool over related budget or ledger tools.

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

All Sivella tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?