Skip to main content
Glama

Locale key coverage

bpj_localization_key_coverage
Read-onlyIdempotent

Compare flat JSON language dictionaries and report missing, extra and blank target translations.

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": {
      "base": "<base>",
      "target": "<target>"
    },
    "name": "bpj_localization_key_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYes
targetYes

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 establish readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description adds useful output-level context by naming the three finding categories, but says nothing about directionality of base vs target, how 'blank' is defined, or how non-flat input is handled.

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, and the result categories are placed at the end where they are most useful. It is arguably a little too terse for a two-parameter tool, but nothing is wasted.

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 does carry the burden of describing results, and it lists the three finding types, which is the key information. It still leaves open the meaning of 'blank', the base-vs-target role mapping, and the expected flat-JSON input form, so it is only partially complete for this complexity.

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 0%, so the description must carry meaning, and it does clarify that both inputs are flat JSON dictionaries and that 'target' holds the translations being checked. However, it does not explain the base/target roles explicitly, nor that the dictionaries are supplied inline as JSON strings of limited size.

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+resource ('Compare flat JSON language dictionaries') and names the report contents (missing, extra, blank target translations), so the agent knows it is a diff/coverage check on locale dictionaries. It does not explicitly distinguish itself from the sibling token-parity or duplicate-key tools, which keeps it 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 only implied by 'compare ... dictionaries'; there is no statement of when to prefer this over token parity or duplicate-key checks, and no prerequisites such as both inputs being the same locale pair. Adequate but with a clear gap.

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.