Skip to main content
Glama
cubicecho

MCP Actual

by cubicecho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Set a category’s budget

set_budget_amount
DestructiveIdempotent

Set the budgeted amount in cents for a category in a specific month, replacing any existing value. Returns updated budgeted, spent, and balance figures so changes are immediately visible.

Instructions

Set the amount budgeted to one category for one month, in integer cents. This replaces the existing amount rather than adding to it. Returns the category’s resulting budgeted/spent/balance figures so the effect is visible immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthYesMonth to budget in, as YYYY-MM.
amountYesAmount to budget, in cents. Replaces the current amount.
categoryIdYesCategory id, from list_categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (destructive, idempotent, openWorld, non-readOnly). The description adds genuinely useful behavior beyond that: the value replaces rather than increments the existing amount, and the resulting budgeted/spent/balance figures are returned so the effect is immediately visible.

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?

Three tight sentences, front-loaded with the core action and scope, then the replace semantics, then the return behavior. No filler, and each sentence earns its place.

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?

With no output schema, the description helpfully discloses the returned budgeted/spent/balance figures, and the replace semantics are covered. It is essentially complete for a 3-param mutation, though it does not mention auth/permission requirements for modifying a budget.

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 description coverage is 100%, so month format, cents, and categoryId sourcing are already documented in the schema. The description restates cents and the replace semantics but adds no syntax or format detail beyond the structured fields; baseline 3 applies.

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?

States a specific verb (set) plus the resource and precise scope (one category, one month, integer cents). This clearly separates it from sibling mutation tools like set_budget_carryover, hold_for_next_month, and sync_budget.

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?

Usage is implied by the operation but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as sync_budget or hold_for_next_month. An agent must infer that this is the direct single-category override path.

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

Deploy Server

Other Tools