Skip to main content
Glama

create_tag

Create a new tag that can be assigned to transactions. Use when the user wants to label or categorize transactions with a custom tag. Returns the created tag with its ID. 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>",
      "color": "<color>"
    },
    "name": "create_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoOptional icon identifier for the tag.
nameYesTag name (must be unique for this user).
colorYesHex color code for the tag (e.g. "#FF5733").
descriptionNoOptional description of the tag.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / color / pattern
      Added value: +"^#[0-9A-Fa-f]{6}$"
    • addedInput schema / properties / description / anyOf
      Added value: +[
      +  {
      +    "maxLength": 500,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / description / type
      Removed value: -"string"
    • addedInput schema / properties / icon / anyOf
      Added value: +[
      +  {
      +    "maxLength": 50,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedInput schema / properties / icon / type
      Removed value: -"string"
    • addedInput schema / properties / name / maxLength
      Added value: +100
    • addedInput schema / properties / name / minLength
      Added value: +1
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations supply only readOnlyHint=false, so the description carries the rest of the burden and does add real value: it discloses that the created tag (with its ID) is returned and that a finance:write scope is required, which is the kind of auth prerequisite an agent needs before calling. It does not state what happens on a duplicate name, even though the schema flags name uniqueness, leaving the main failure mode undisclosed.

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 short sentences, front-loaded with the action and followed by the usage trigger, the return shape, and the auth requirement. No filler or redundant 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 simple four-parameter creation tool with a rich schema and no output schema, the description covers purpose, trigger, return shape, and scoping. The only meaningful gap is error behaviour on a duplicate tag name, which is relevant given the uniqueness constraint called out in the schema.

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 every parameter (name, color, icon, description) is already documented with types, formats, and constraints like the hex-color pattern. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 tag that can be assigned to transactions." That clearly separates it from delete_tag and update_tag in the sibling list. It does not explicitly distinguish itself from create_category or create_payee, which are the closest conceptual neighbours, so it falls just short of a 5.

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?

"Use when the user wants to label or categorize transactions with a custom tag" gives a concrete trigger condition for invocation. There is no when-not guidance, though, and the word "categorize" overlaps semantically with the sibling create_category tool, which an agent could plausibly confuse with this one.

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.