Skip to main content
Glama

create_category

Create a new transaction category. Supports nested categories via parentId — child categories inherit the parent color if none is provided. Use when the user wants a new category to classify transactions. 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": {
      "name": "<name>"
    },
    "name": "create_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoOptional icon identifier for the category.
nameYesCategory name.
typeNoCategory type: "custom" (default, user-editable) or "internal" (system-managed).
colorNoHex color code (e.g. "#4CAF50"). Inherited from parent if omitted.
parentIdNoID of the parent category to create a subcategory.
defaultTagIdsNoTag IDs (from get_tags) that new transactions in this category get by default. Max 20
applyDefaultTagsOnAiCategorizationNotrue also applies defaultTagIds when AI categorization picks this category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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"
      +}
    • addedInput schema / properties / color / pattern
      Added value: +"^#[0-9A-F]{6}$"
    • addedInput schema / properties / defaultTagIds
      Added value: +{
      +  "description": "Tag IDs (from get_tags) that new transactions in this category get by default. 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
    • removedInput schema / properties / parentId / 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)$"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description usefully adds the write-permission requirement ("Requires finance:write scope") and the inheritance behavior for nested categories. It stops short of describing what is returned after creation (e.g., the new category ID for follow-up calls) or name-uniqueness constraints.

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?

Four short sentences, front-loaded with the core action and followed by the nesting behavior and precondition. The color-inheritance clause partly duplicates the schema, which is the only wasted material.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 and only a readOnly hint, the description covers the action, nesting, and auth scope, but leaves the agent guessing about the response payload and any error conditions. Adequate to call correctly, not fully complete for a create operation whose result is likely needed downstream.

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 all seven parameters, including the enum for type and the pattern for color, are already documented. The description restates the color-inheritance rule that the color property itself already states, and adds only mild framing for parentId as subcategory creation — the schema still does the heavy lifting, so 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?

The description opens with a specific verb and resource ("Create a new transaction category"), which cleanly separates it from update_category and delete_category among the siblings. An agent knows exactly what object is being produced 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?

It provides a clear trigger condition: "Use when the user wants a new category to classify transactions." It does not state when NOT to use it (e.g., when an existing category should be reused, or to point at update_category for renaming), but the positive guidance is unambiguous.

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.