Skip to main content
Glama

Tag keys

tag_keys

Add tags to translation keys. Creates tags if they don't exist.

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": {
      "keyNames": "<keyNames>",
      "tags": "<tags>"
    },
    "name": "tag_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsYesNames of the tags to add
branchNoOptional: branch name
keyNamesYesNames of the keys to tag
namespaceNoOptional: namespace of the keys
projectIdNoID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / projectId / description
      Previous value: -"ID of the project (required for PAT, auto-resolved for PAK)"New value: +"ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false and destructiveHint=false, so the write-but-not-destructive profile is known. The description adds one genuinely useful behavioral detail beyond that: tags are auto-created when missing (upsert semantics). It still omits whether existing key tags are replaced or appended, and how unknown key names are handled.

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?

Two short sentences, front-loaded with the action and followed immediately by the side effect. Nothing is wasted, though the extreme brevity means some could-be-useful context is absent rather than trimmed.

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?

With five parameters fully documented in the schema, no output schema, and annotations covering the safety profile, the description only needs to state the action and any non-obvious side effect, which it does. The remaining gap around append-vs-replace semantics is modest but real for a tagging mutation.

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 (tags, keyNames, branch, namespace, projectId) is documented in the schema, including the projectId credential-binding note. The description adds no additional meaning about parameter interaction or formats, so the baseline 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?

"Add tags to translation keys" gives a specific verb (add) and resource (tags on translation keys), which is enough to separate it from list_tags or create_keys. It does not explicitly name a sibling to distinguish itself from, keeping it just below 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus alternatives such as list_tags (to inspect existing tags first) or update_key. No prerequisites, no mention of what happens when a key name doesn't exist, and no exclusions.

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.