Multilocale

Export one language's strings

export_locale_dictionary

Read-onlyIdempotent

Use this when someone wants the key and value pairs of one language, for example to review or copy a translation file. Returns up to 50 entries per call (25 by default) sorted by key, values cut to 500 characters, with nextSkip for the next page. Not for a complete file download, which the MultiLocale CLI provides.

Input Schema

TableJSON Schema

Name	Required	Description
`skip`	No	Keys to skip in alphabetical order, for paging: pass the previous nextSkip; defaults to 0, at most 10000
`limit`	No	Entries to return, from 1 to 50; defaults to 25
`project`	Yes	Project name; an id matches nothing
`language`	Yes	Locale code to export, such as en

Output Schema

TableJSON Schema

Name	Required	Description
`skip`	Yes
`status`	Yes
`entries`	Yes	Key and value pairs sorted by key, values cut to 500 characters
`hasMore`	Yes
`project`	Yes
`language`	Yes
`nextSkip`	Yes	Pass as skip to get the next page; null on the last page
`returnedCount`	Yes
`valuesTruncated`	Yes
`offsetCapReached`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 28, 2026

changedInput schema / properties / language / description

Previous value: -"Language code to export (for example, en)"New value: +"Locale code to export, such as en"

changedInput schema / properties / limit / description

Previous value: -"Maximum number of keys to return. Defaults to 25, capped at 50."New value: +"Entries to return, from 1 to 50; defaults to 25"

changedInput schema / properties / project / description

Previous value: -"Project name (slug) to export"New value: +"Project name; an id matches nothing"

changedInput schema / properties / skip / description

Previous value: -"Number of keys to skip, sorted alphabetically. Defaults to 0 and is capped at 10000."New value: +"Keys to skip in alphabetical order, for paging: pass the previous nextSkip; defaults to 0, at most 10000"

addedOutput schema / properties / entries / description

Added value: +"Key and value pairs sorted by key, values cut to 500 characters"

addedOutput schema / properties / nextSkip / description

Added value: +"Pass as skip to get the next page; null on the last page"

First observedAug 30, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Despite annotations already covering readOnly/idempotent/non-destructive, the description adds substantial behavior: page size (25 default, 50 max), alphabetical sort by key, 500-character value truncation, and the nextSkip paging contract. This is exactly the operational detail an agent needs to page correctly.

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?

Two sentences, front-loaded with the use case followed by the behavioral/paging contract and the exclusion. No filler and every clause carries information.

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 annotations covering safety and a full output schema plus 100% parameter coverage, the description only needs to add operational context – and it does, via paging, sorting, and truncation limits, plus a pointer away from the CLI for full downloads.

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%, so all four parameters are already documented with defaults and bounds. The description's mention of 50/25 and nextSkip largely restates the schema, adding paging semantics but no new parameter-level meaning; 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 states a specific verb and resource: returning key/value pairs for a single language, tagged by intent ("to review or copy a translation file"). It explicitly rules out a complete file download, though it does not distinguish itself from sibling tools like list_phrases or search_phrases, which also surface phrase data.

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?

It gives both a positive trigger (reviewing or copying a translation file) and an explicit exclusion (complete file download belongs to the MultiLocale CLI). The exclusion points at a non-MCP alternative rather than a sibling tool, so the routing guidance is clear but not fully connected to the tool list.

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?