Simpler.Asia

expense_category_delete

DestructiveIdempotent

Deletes a custom category — categories are tenant-shared, so any tenant member can remove one regardless of who created it; the 9 seeded defaults are undeletable and refuse with CONFLICT (default_category: true). Expenses already carrying the deleted category keep their category_id untouched and simply render as Uncategorized; nothing is reassigned or blocked.

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": {
      "id": "<id>"
    },
    "name": "expense_category_delete"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The expense_category id (expense_category_list shows them).
`icon`	No
`name`	No
`slug`	No
`color`	No
`is_default`	No
`sort_order`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the destructiveHint/idempotentHint annotations: tenant-wide blast radius (any member can delete regardless of creator), the exact failure mode and error payload for defaults, and the post-delete referential behavior (expenses keep category_id and render as Uncategorized, nothing reassigned or blocked). That is precisely the information an agent needs before an irreversible action.

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?

One front-loaded sentence that starts with the action, then layers scope, failure mode, and side effects in priority order. No filler, no restatement of the tool name.

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 destructive tool with no output schema, it covers permissions, error behavior, and consequences for referencing expenses. The remaining hole is the unexplained extra parameters.

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 14% (only 'id' is documented), yet the description says nothing about parameters. Worse, the schema exposes six extra properties (icon, name, slug, color, is_default, sort_order) on a delete operation with no explanation of whether they are ignored or used for matching — a real ambiguity the description should resolve.

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 and resource ('Deletes a custom category') and immediately narrows scope: custom-only, tenant-shared, seeded defaults excluded. An agent can distinguish this from expense_category_update/expense_category_list without opening any schema.

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

Usage Guidelines4/5

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

Gives a clear when-not-to-use rule (the 9 seeded defaults are undeletable and return CONFLICT with default_category: true), which prevents a whole class of failed calls. It does not name a sibling alternative for renaming/recoloring (e.g. expense_category_update), so routing is slightly incomplete.

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

All Simpler.Asia 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?