Skip to main content
Glama
erikrubstein

monarch-mcp2

by erikrubstein

Budget Clear Budget

budget_clear_budget
Destructive

Reset or delete budget data for a specified month. Use to clear, remove, or reset budget entries after confirmation.

Instructions

Clear budget. This may delete, clear, reset, or otherwise remove data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthYes
fieldsNoOptional dotted output field paths to return, such as ['id', 'merchant.name', 'category.name'].
confirmNo
output_modeNoOutput shape to return. Use summary for compact CLI-style defaults, full for complete structured data without raw, and raw for complete structured data including raw payloads.summary
session_pathNo
Behavior3/5

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

The description aligns with annotations (destructiveHint=true) by mentioning potential data removal. However, it adds minimal context beyond what annotations already indicate, and the openWorldHint is not explained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very brief (one sentence) and gets to the point. However, the brevity sacrifices necessary detail.

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?

With 5 parameters, no output schema, and a destructive action, the description is insufficient. It doesn't explain the meaning of 'confirm', what fields do, or the implications of openWorldHint=true.

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 40% (2 of 5 parameters have descriptions). The tool description does not explain any parameters or their roles, leaving agents to rely on the schema alone, which is incomplete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action (clear) and resource (budget), but fails to distinguish from sibling tools like budget_reset_budget. The wording 'may delete, clear, reset, or otherwise remove data' is vague and does not clarify what clearing a budget entails compared to resetting.

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?

No guidance on when to use this tool versus alternatives (e.g., budget_reset_budget, budget_delete_budget). No context about prerequisites or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/erikrubstein/monarch-mcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server