Modify an existing Lunch Money category by updating its name, description, income flag, budget/totals exclusions, archive status, or group assignment using the category ID.
Update an existing Lunch Money category.
| Name | Required | Description | Default |
|---|---|---|---|
| category_id | Yes | ||
| name | No | ||
| description | No | ||
| is_income | No | ||
| exclude_from_budget | No | ||
| exclude_from_totals | No | ||
| archived | No | ||
| group_id | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It only says 'update' without disclosing return behavior, idempotency, or authentication requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence, but it is too brief and lacks any structuring (e.g., sections, bullet points).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 8 parameters and no output schema, the description is severely incomplete. It fails to explain what the tool returns or any side effects.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description adds no meaning to any of the 8 parameters. Parameters are completely undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'update' and the resource 'category', distinguishing it from create_category and get_categories. However, it lacks specifics on which fields can be updated, but the purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like create_category. No conditions or prerequisites are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/robshox/lunchmoney-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server