Skip to main content
Glama

Translation argument parity

bpj_localization_token_parity
Read-onlyIdempotent

Compare names and multiplicities of simple braced identifier tokens in a source string and translation.

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": {
      "original": "<original>",
      "translation": "<translation>"
    },
    "name": "bpj_localization_token_parity"
  }
}

Input Schema

NameRequiredDescriptionDefault
originalYes
translationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds one useful scoping detail — only 'simple braced identifier tokens' are compared, implying complex/nested formats are out of scope — but says nothing about how multiplicity differences are reported or how matching is performed (case, ordering).

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 front-loaded sentence with no filler, stating verb, compared property, and both inputs. It is tight, though the density of qualifiers ('simple braced identifier tokens') could be unpacked slightly for clarity.

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 no output schema, the description should indicate the shape of the comparison result (missing, extra, or duplicated tokens), which it does not. For a two-string parity check this leaves the agent unable to predict the return value or interpret a 'multiplicity' mismatch.

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 0%, so the description carries the burden; it does explain that both inputs are strings containing braced identifier tokens to be compared. However, it does not clarify the expected token syntax (e.g., {name} vs {0}), whether empty strings are valid, or what 'multiplicity' means for repeated tokens.

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 gives a specific verb ('Compare') and a precise resource ('names and multiplicities of simple braced identifier tokens in a source string and translation'). It is specific enough to separate it from siblings like bpj_translation_length_expansion or bpj_translation_conflict_review, though it does not name any 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 Guidelines3/5

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

The comparison of source vs. translation implies the intended use (placeholder/argument parity checking before or after translation), but there is no explicit when-to-use, when-not-to-use, or alternative routing guidance. The agent must infer the workflow context.

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.