Skip to main content
Glama

Update key

update_key
Destructive

Update an existing translation key's name, namespace, or description

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": {
      "keyName": "<keyName>",
      "newName": "<newName>"
    },
    "name": "update_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNameYesCurrent key name (used to find the key)
newNameYesNew key name (provide the current name if unchanged)
keyBranchNoOptional: branch name (used to find the key, for branching projects)
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.
keyNamespaceNoOptional: current namespace of the key (used to find the key)
newNamespaceNoOptional: new namespace for the key
newDescriptionNoOptional: new description for the key

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

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that: it never warns that renaming a key can break translation references or tooling, whether the change is reversible, or what permissions are required. For a destructive mutation, that is a real gap.

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?

A single efficient sentence with no filler, front-loading the verb and resource. It is perhaps too terse rather than bloated, but nothing in it is wasted.

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?

With seven parameters, a fully documented schema, and annotations carrying the destructive flag, the definition is minimally sufficient to invoke the tool. It is incomplete for the rename case, where an agent would benefit from knowing the effect on linked translations and whether the old key name remains valid.

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 is already documented in the schema, including the non-obvious 'provide the current name if unchanged' rule. The description only echoes the field list and adds no extra meaning about lookup semantics or branch behavior.

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 states a specific verb ('Update') and resource ('an existing translation key') plus the three mutable fields (name, namespace, description). It is clearly distinguishable from create_keys, delete_keys, and get_key, though it does not name a sibling explicitly.

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 when-to-use guidance: nothing says whether to reach for update_key versus delete_keys+create_keys when renaming, nor any prerequisite such as the key having to exist first. Usage is only inferable from the word 'existing'.

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.