Skip to main content
Glama

create_tag

Create a standalone group/tag without selecting or changing any expenses. The first call prepares a preview; after the user explicitly chooses to create it, send confirm:true with the returned operationId (fresh duplicate checks run). A first call with confirm:true still returns a preview. An exact canonical duplicate is a no-op; archived tags are not reactivated. Similar names are returned as choices; set allowSimilar:true only when the user explicitly chooses a distinct new group despite them. Use list_tags to inspect all groups.

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

Input Schema

NameRequiredDescriptionDefault
nameYesName of the new group/tag.
statusNoWhen true, read the verified outcome for operationId without creating or changing a tag.
confirmNoConfirm only after the user approves the preview; a first confirm call remains preview-only.
operationIdNoServer-issued preview operation ID to confirm a staged create.
allowSimilarNoAllow creation alongside similar names only when the user explicitly chooses a new distinct group.

Output Schema

NameRequiredDescriptionDefault
nameNo
errorNo
statusNo
choicesNo
createdNo
messageNo
successYes
retryableNo
existingTagNo
operationIdNo
similarTagsNo
confirmationNo
existingTagsNo
previewStaleNo
canonicalNameNo
requestedNameNo
existingMatchesNo
outcomeVerifiedNo
existingTagCountNo
groupManagementUrlNo
confirmationRequiredNo
requiresConfirmationNo
existingTagsTruncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • removedOutput schema / properties / choices / items / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / choices / items / properties
      Removed value: -{
      -  "isActive": {
      -    "type": "boolean"
      -  },
      -  "kind": {
      -    "type": "string"
      -  },
      -  "name": {
      -    "type": "string"
      -  },
      -  "params": {
      -    "type": "object"
      -  }
      -}
    • removedOutput schema / properties / confirmation / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / confirmation / properties
      Removed value: -{
      -  "actionId": {
      -    "type": "string"
      -  },
      -  "allowSimilar": {
      -    "type": "boolean"
      -  },
      -  "confirm": {
      -    "type": "boolean"
      -  },
      -  "name": {
      -    "type": "string"
      -  },
      -  "operationId": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / error / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / error / properties
      Removed value: -{
      -  "code": {
      -    "type": "string"
      -  },
      -  "message": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / existingMatches / items / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / existingMatches / items / properties
      Removed value: -{
      -  "isActive": {
      -    "type": "boolean"
      -  },
      -  "tag": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / existingTag / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / existingTag / properties
      Removed value: -{
      -  "isActive": {
      -    "type": "boolean"
      -  },
      -  "tag": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / existingTags / items / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / existingTags / items / properties
      Removed value: -{
      -  "isActive": {
      -    "type": "boolean"
      -  },
      -  "tag": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / groupManagementUrl / format
      Removed value: -"uri"
    • removedOutput schema / properties / similarTags / items / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / similarTags / items / properties
      Removed value: -{
      -  "isActive": {
      -    "type": "boolean"
      -  },
      -  "score": {
      -    "type": "number"
      -  },
      -  "tag": {
      -    "type": "string"
      -  }
      -}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond openWorldHint=false/destructiveHint=false, the description discloses genuinely non-obvious behavior: fresh duplicate checks run on confirmation, a first confirm:true call still only previews, exact canonical duplicates are a no-op, and archived tags are silently not reactivated. These are exactly the traps an agent would otherwise fall into.

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?

Dense but front-loaded: the preview/confirm workflow comes before the duplicate and similar-name edge cases, and the sibling pointer closes it. The line "A first call with confirm:true still returns a preview" partially restates the preceding sentence but earns its place as an explicit guard against a common misuse.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, two-phase staged mutation with an output schema available for return values, the description covers the workflow, the idempotency behavior, and the confirmation gate without needing to explain response shape.

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 100%, so the baseline is 3, but the description goes further by explaining the interplay between confirm and operationId and the precondition for allowSimilar (only when the user explicitly chooses a distinct group). The status parameter's read-verified-outcome path is left to the schema description.

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 plus its scope boundary: "Create a standalone group/tag without selecting or changing any expenses." That negatives clause distinguishes it cleanly from expense-mutating siblings in a way the name alone would not.

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 spells out the call sequence (preview first, then confirm:true with the returned operationId), when to set allowSimilar, and points to list_tags for inspection. It stops short of stating when this tool should not be used versus other creation paths, so a 4 rather than a 5.

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.