Skip to main content
Glama

update_category

Update an existing category by ID. Use when the user wants to rename, recolor, re-icon, move or set the default tags of a category. Returns the updated category records. Requires finance:write scope.

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": {
      "categoryId": "<categoryId>"
    },
    "name": "update_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoNew icon identifier, or null to clear it.
nameNoNew category name.
colorNoNew hex color code (e.g. "#4CAF50").
parentIdNoMove under this parent category ID, or null to make it top-level. Omit to keep it where it is
categoryIdYesID of the category to update.
defaultTagIdsNoReplaces the default tags (IDs from get_tags); [] clears them. Max 20
applyDefaultTagsOnAiCategorizationNotrue also applies defaultTagIds when AI categorization picks this category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / applyDefaultTagsOnAiCategorization
      Added value: +{
      +  "description": "true also applies defaultTagIds when AI categorization picks this category",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / categoryId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • addedInput schema / properties / color / pattern
      Added value: +"^#[0-9A-F]{6}$"
    • addedInput schema / properties / defaultTagIds
      Added value: +{
      +  "description": "Replaces the default tags (IDs from get_tags); [] clears them. Max 20",
      +  "items": {
      +    "format": "uuid",
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • changedInput schema / properties / icon / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 50,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / name / maxLength
      Added value: +200
    • addedInput schema / properties / name / minLength
      Added value: +1
    • addedInput schema / properties / parentId
      Added value: +{
      +  "anyOf": [
      +    {
      +      "format": "uuid",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Move under this parent category ID, or null to make it top-level. Omit to keep it where it is"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the single readOnlyHint=false annotation, the description discloses the required 'finance:write' scope and that the call returns the updated category records, both of which matter for a mutation tool. It does not discuss failure behavior (e.g. invalid parentId, unknown tag IDs) or whether omitted fields are preserved, though the schema partly covers the latter.

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 sentences with no filler: identity, selection trigger, then return/auth facts. Front-loaded with the core action and progressively adding decision-relevant detail.

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 7-parameter mutation tool with no output schema, the definition covers what it does, when to use it, what it returns and the auth scope, which is most of what an agent needs. The remaining gap is error/partial-update semantics, which is minor here since the schema documents the omit-vs-null distinction.

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 field-level meaning (null to clear icon, null parentId to promote to top-level, [] to clear tags) is already fully documented in the schema. The description's field enumeration is user-facing framing that adds little syntax or constraint detail beyond what the schema already provides, so the 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 and resource ('Update an existing category by ID') and then enumerates the exact mutations supported (rename, recolor, re-icon, move, default tags). An agent can distinguish it from create_category, delete_category and update_tag 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?

The second sentence gives a clear user-intent trigger ('Use when the user wants to rename, recolor, re-icon, move or set the default tags'), which maps directly to the request patterns that should select this tool. It stops short of naming exclusions or pointing to siblings like update_tag or delete_category for the adjacent operations.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.