Skip to main content
Glama

Locale picker review

review_locale_picker
Read-only

Reviews a language or region switcher. Pass locales as markup (a with options, or a list of links with hreflang or lang) or as lines such as de: Deutsch. Flags flag emoji or flag imagery standing in for languages, options named in English instead of their own language (autonym), options shown only as a code, missing lang on options (WCAG 3.1.2 Language of Parts), invalid BCP 47 tags, labels that differ from the usual autonym in a built-in table of about 30 languages, RTL options without dir, duplicates, unsorted long lists, a select that navigates on change (WCAG 3.2.2 On Input), an unlabeled select (4.1.2), and language mixed with region. Static; it does not load the target pages.

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": {
      "locales": "<locales>"
    },
    "name": "review_locale_picker"
  }
}

Input Schema

NameRequiredDescriptionDefault
localesYesSwitcher markup, or lines like `de: Deutsch`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/destructive=false; the description adds real value beyond them by disclosing that comparison uses 'a built-in table of about 30 languages' (an important coverage limitation) and by tying flags to specific WCAG criteria (3.1.2, 3.2.2, 4.1.2). It does not say how findings are shaped or whether severity is reported.

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?

Front-loaded with purpose, then input contract, then a compact enumeration of detected defects, with no filler sentences. The defect list is a single long run-on chain, which is dense but each clause maps to a distinct check, so little is wasted.

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?

With one parameter and no output schema, an agent mainly needs to know accepted input, scope limits, and what a review yields; input and scope are covered and the flag list implies actionable findings. The missing piece is the response shape (per-issue list vs. summary, severity or line references).

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% and already states the two accepted forms, so baseline is 3; the description earns one more by spelling out concrete formats (options in a select, links with hreflang or lang, colon-delimited lines) and by implying one switcher per call. It adds no constraints such as size limits or multi-switcher handling.

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?

States a specific verb and resource ('Reviews a language or region switcher') and enumerates the exact defects it detects, which no sibling (localisation_readiness, stress_test_localisation, plan_text_expansion) covers at this artifact level. The closing scope note 'Static; it does not load the target pages' further pins the boundary.

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

Usage Guidelines4/5

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

Gives clear acceptance formats for the input (a <select> with options, a list of links with hreflang/lang, or lines like `de: Deutsch`) and states the static/no-fetch limitation. It never names a sibling for adjacent tasks (e.g. whole-page localisation checks), so routing to alternatives is left to inference.

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