Multilocale

Find missing translations

find_missing_translations

Read-onlyIdempotent

Use this when someone asks which strings are not translated yet, or how complete each language is. Returns completion percentages and up to 25 missing keys per locale, for one locale or up to 10, compared with the default locale. Nothing is translated or written. Not for filling in the missing translations.

Input Schema

TableJSON Schema

Name	Required	Description
`project`	Yes	Project id or name
`language`	No	One locale code to check; omit to check the configured locales
`scanLimit`	No	Strings to scan per locale, from 1 to 2000; defaults to 1000
`localeLimit`	No	How many configured locales to check when language is omitted, from 1 to 10; defaults to 10

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes
`locales`	Yes	One row per checked locale with its completion and up to 25 missing keys; status partial means a scan cap was reached
`project`	Yes
`scanLimit`	Yes
`defaultLocale`	Yes
`localesTruncated`	Yes
`sourceScanTruncated`	Yes
`sourcePhrasesScanned`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 28, 2026

changedInput schema / properties / language / description

Previous value: -"Locale code to check. Omit to report coverage for every configured locale."New value: +"One locale code to check; omit to check the configured locales"

changedInput schema / properties / localeLimit / description

Previous value: -"Maximum configured locales to check when language is omitted. Defaults to 10."New value: +"How many configured locales to check when language is omitted, from 1 to 10; defaults to 10"

changedInput schema / properties / project / description

Previous value: -"Project id or name whose translation coverage should be checked"New value: +"Project id or name"

changedInput schema / properties / scanLimit / description

Previous value: -"Maximum phrases to scan per locale. Defaults to 1000, capped at 2000."New value: +"Strings to scan per locale, from 1 to 2000; defaults to 1000"

addedOutput schema / properties / locales / description

Added value: +"One row per checked locale with its completion and up to 25 missing keys; status partial means a scan cap was reached"

First observedAug 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/destructiveHint=false, and the description reinforces this with 'Nothing is translated or written.' It also adds concrete behavioral caps not in the annotations: up to 25 missing keys per locale, 1 or up to 10 locales, and comparison against the default locale.

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

Conciseness5/5

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

Three sentences, zero filler: the trigger comes first, the return shape second, the scope and exclusion last. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full schema, annotations covering the safety profile, and an output schema present, the description supplies everything else an agent needs: trigger, return granularity, locale bounds, and the read-only guarantee.

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 its parameter descriptions already explain language, scanLimit, and localeLimit including the 1-10 range and default. The description's 'for one locale or up to 10' largely restates the localeLimit schema text rather than adding new meaning, so baseline 3 applies.

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 ('which strings are not translated yet', completion completeness) and explicitly bounds scope against the fill-in sibling: 'Not for filling in the missing translations.' An agent can tell this apart from update_phrase/add_phrase without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use this when someone asks which strings are not translated yet, or how complete each language is') plus an explicit exclusion ('Not for filling in the missing translations'), which is exactly the when/when-not framing needed next to mutation siblings like add_phrase.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Multilocale tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?