Skip to main content
Glama

translation-invariants

Check that numbers, units, part numbers, tolerance signs, dates, placeholders and URLs survive translation — For aligned source and target segments, extracts the tokens a translation must not change (numbers with attached units or %, ISO dates, part numbers and versions, tolerance and comparison operators such as ± ≤ ≥, placeholders like {0} or %s, URLs and emails) and reports any that are missing, added or altered, with offsets in both texts in UTF-16, code points, UTF-8 bytes and graphemes. Numbers are

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": {
      "segments": "<segments>"
    },
    "name": "translation-invariants"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindsNoToken kinds to check. Default all.
segmentsYesUp to 200; 100000 characters in total.
sourceDecimalNoDecimal mark of the source locale. Default auto (both readings tried).
targetDecimalNoDecimal mark of the target locale. Default auto.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 does disclose the detection categories and that the report includes missing/added/altered tokens with offsets in four coordinate systems, plus that decimal marks default to 'auto' (both readings tried). However, the trailing fragment 'Numbers are' truncates what may have been important behavior about numeric normalization, and nothing is said about error handling or result ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key scope statement is front-loaded and the parenthetical token list is informative rather than padded. But the description ends mid-sentence with 'Numbers are,' leaving a dangling fragment that is both wasted text and a loss of information.

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?

For a pure-analysis tool with no annotations and no output schema, the description does reasonably well by enumerating what the report contains and the offset encodings. It nevertheless stops short of describing the response shape explicitly and cuts off before finishing its explanation of numeric handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description earns above that by expanding the `kinds` enum with concrete examples (units/%, ISO dates, versions, ± ≤ ≥, {0}/%s, emails) that clarify what belongs to each category. It also touches on decimal-mark handling, though the truncated final sentence limits how much it adds for sourceDecimal/targetDecimal.

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 names a specific verb-plus-resource: extract invariant tokens (numbers with units/%, ISO dates, part numbers, versions, operators, placeholders, URLs/emails) from aligned source/target segments and report any that are missing, added, or altered. An agent knows exactly what the tool checks, though it makes no explicit contrast with any alternative approach.

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?

Usage is implied by the phrase 'For aligned source and target segments,' which tells the agent the required input shape (paired segments), but there is no statement of when to prefer this over other QA tools, no prerequisites, 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.

Resources