Simpler.Asia

expense_category_update

Edits a category's name, icon, color, or sort_order — slug and is_default are the category's fixed identity, and any attempt to change either refuses with VALIDATION_ERROR. color, when given, must be a #rrggbb hex value. Create a new category instead of trying to rename an existing slug.

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_update"
  }
}

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
`expected_updated_at`	No	Optional compare-and-set guard: the updated_at you last read. Mismatch returns CONFLICT with the current value.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish that this is a non-destructive, non-idempotent mutation. The description adds useful behavior beyond annotations: slug and is_default are immutable, attempts to change them return VALIDATION_ERROR, and color must be a #rrggbb hex value.

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?

The description is front-loaded with the editable fields, then immediately covers immutable identity and validation behavior, and closes with the correct alternative for slug renames. Every sentence adds relevant information with no filler.

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 an 8-parameter mutation with no output schema and low schema coverage, the description provides the key constraints an agent needs: editable fields, fixed fields, validation error behavior, and color format. Minor details like sort_order semantics and expected_updated_at are adequately covered by the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, so the description must compensate. It meaningfully clarifies that name/icon/color/sort_order are editable while slug/is_default are fixed identity fields, and it documents the color format; it leaves icon length and sort_order semantics to the schema.

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 ('Edits') and resource ('category') and enumerates the editable fields: name, icon, color, and sort_order. It explicitly distinguishes this from expense_category_create for slug renames and marks slug/is_default as fixed identity, so an agent can identify the tool without opening the 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?

Explains when to use it for edits to name/icon/color/sort_order and directs slug renames to create. It does not discuss other siblings like expense_category_list or expense_category_read, but the key exclusions and alternative are clear.

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?