Skip to main content
Glama

glossary_apply

Validates target strings against a glossary, enforcing term consistency and flagging untranslated source terms or brand-term variants deterministically.

Instructions

Enforce glossary/term consistency across target strings. Flags untranslated source terms and brand-term variants. Deterministic.

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": {
      "glossary": "<glossary>",
      "items": "<items>"
    },
    "name": "glossary_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesStrings to check: {key?,text}.
glossaryYesTerms: {source,target} for translation pairs, or {source,keep:true} for brand/proper terms that must stay verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the tool flags untranslated source terms and brand-term variants and that behavior is deterministic, which is real behavioral information. However, "Enforce" implies mutation while "Flags" implies read-only detection, and the description never resolves whether input strings are modified or merely reported on.

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 core action and followed by the detection scope and a behavioral qualifier. No filler and nothing buried at the end.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description leaves the critical question unanswered: does it return a list of violations, rewritten strings, or mutate in place? The enforce-vs-flag ambiguity is exactly what an agent needs resolved before calling this on target strings.

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 both parameters are already documented, including the {source,target} and {source,keep:true} forms. The description reinforces the intent (brand terms "must stay verbatim") but adds no syntax or format detail beyond the schema, making the baseline 3 correct.

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?

States a specific verb and resource ("Enforce glossary/term consistency across target strings") and names the concrete defects it detects ("untranslated source terms and brand-term variants"), so the domain is unmistakable. It does not explicitly contrast itself with the sibling i18n_lint, which likely overlaps in the linting/consistency space, so differentiation stops 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative such as i18n_lint or localize. The agent must infer from the purpose alone whether this is the right tool for a given consistency check.

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