Skip to main content
Glama
Sign In
i18n-mcp

i18n-mcp

by skk2010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_key

Remove a translation key from all or selected locales, and prune empty parent keys in Rails-style YAML/JSON files.

Instructions

Delete a key from locales (default: all); prunes empty parents.

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": {
      "key": "<key>"
    },
    "name": "delete_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesDot-separated key path, e.g. "roles_scope.super_admin"
localesNoDefault: all locales

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It discloses the side effect of pruning empty parents and the default locale scope, which is useful. However, it omits other destructive-operation details like reversibility or return values, though the verb 'Delete' signals irreversibility.

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?

The description is a single, front-loaded sentence that immediately states the action and resource, then adds a concise behavioral note. No wasted words, earns its place.

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?

Given the tool's simplicity (2 params, no output schema, no annotations), the description adequately covers the purpose, scope, and a key side effect. A minor gap is the lack of explicit error or return behavior, but this is not required without an output 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 the baseline is 3. The description adds no extra parameter meaning beyond what the schema already contains; the 'default: all' for locales is duplicated from the schema.

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 clearly states the tool deletes a key from locales, with a specific verb and resource. It distinguishes itself from siblings like get_key, set_key, and search by the 'Delete' action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage (when you want to delete a key) and notes the default behavior (all locales), but does not explicitly compare alternatives or state when not to use it. No exclusion criteria or alternative tool references are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools