Skip to main content
Glama

i18n Glossary Check

glossaire_bilingue

Glossaire bilingue : aligne les clés de deux catalogues de traduction et signale les traductions manquantes ainsi que tout paramètre interpolé (ex. {montant}) perdu ou ajouté par une traduction.

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": {
      "source": "<source>",
      "cible": "<cible>"
    },
    "name": "glossaire_bilingue"
  }
}

Input Schema

NameRequiredDescriptionDefault
cibleYesCatalogue traduit à contrôler contre la source.
sourceYesCatalogue de référence : clé -> texte, paramètres entre accolades.

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 usefully discloses the two classes of findings (missing translations, lost/added interpolated parameters like {montant}), which is real behavioral value, but it never states that the tool is read-only and never says whether it mutates or merges the catalogs, nor what the result looks like.

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 that front-loads the resource name and then the outputs, with no filler. It is slightly dense and mixes purpose with result-detail in one clause, but nothing is wasteful.

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 tool with zero annotations, no output schema, and nested-object parameters, the definition explains intent and detection categories but leaves the return shape (aligned glossary? issue list? counts?) undefined. Adequate to select the tool, not fully adequate to know what to expect back.

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 coverage is 100% and both parameters ('source', 'cible') are already documented in the schema, including the 'paramètres entre accolades' convention. The description reinforces the role of each side but adds no format, key-matching rule, or edge-case semantics beyond the schema, so the baseline 3 applies.

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 concrete verb pair ('aligne les clés', 'signale') and a concrete resource ('deux catalogues de traduction'), so the agent knows exactly what operation is performed. It does not need sibling differentiation because no siblings exist, which keeps it just below 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 Guidelines3/5

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

Usage is implied: comparing a reference catalog against a translated one to catch gaps and interpolation-parameter mismatches. There is no explicit statement of when not to use it, no mention of prerequisites (both catalogs must share key space), and no alternatives to weigh against.

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