Skip to main content
Glama
Sign In

Sivella

by ai.sivella.mcp
OverviewDiscussionsAdmin

Set a category budget

set_category_budget
Destructive

Propose setting a category's monthly budget limit for a ledger. Proposes only — awaiting confirmation. limit_cents is MINOR units (cents): pass 50000 for a 500.00 limit, never a decimal.

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>",
      "category": "<category>",
      "month": "<month>",
      "limit_cents": "<limit_cents>"
    },
    "name": "set_category_budget"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthYesCalendar month as YYYY-MM.
categoryYesCategory slug or name. Call list_budget_categories first if unsure.
ledger_idYes
limit_centsYesMonthly limit in minor units (cents). 50000 = 500.00.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations mark this non-read-only and destructive, and the description meaningfully qualifies that by disclosing the write is staged rather than immediate ('Proposes only — awaiting confirmation'), which an agent needs in order to sequence a confirm_change call. It also reinforces the unit contract emphatically ('never a decimal'). It does not explain what a proposal returns or whether repeated proposals on the same category overwrite one another.

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?

Two short sentences with no filler: the proposal semantics come first, then the unit rule that is the most likely source of caller error. Nothing is repeated or wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter write tool with annotations and no output schema, this covers the two things an agent most needs: that the effect is a proposal, and the cents convention. The remaining gap is the follow-up path — which tool confirms or discards the proposal — which is left implicit.

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 75%, so the baseline is 3; the description only re-emphasizes limit_cents with a worked example (50000 = 500.00), which the schema already states. It adds nothing for ledger_id or month and does not clarify what 'category' accepts beyond the schema's own note.

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 opens with a specific verb and resource: 'Propose setting a category's monthly budget limit for a ledger', scoped to a ledger and a monthly period. An agent can tell it apart from read-style siblings like get_category_breakdown. It stops short of naming how it differs from set_budget_goal, which is the nearest-sounding sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Proposes only — awaiting confirmation' implies this belongs in a propose-then-confirm workflow, which is real usage guidance. However, it never states when to pick this over set_budget_goal, nor does it name the confirmation step or tool. The prerequisite hint about listing categories lives in the schema, not the description.

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

All Sivella toolsInspect
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