Skip to main content
Glama
Sign In

Multilocale Translations

by com.multilocale
OverviewDiscussionsAdmin

Search strings by text

search_phrases
Read-onlyIdempotent

Use this when someone asks to find translation strings that contain a word or phrase, in their keys or text. Returns up to 100 matches with id, key, language and value from a case-insensitive match within one project. Not for one exact key.

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": {
      "project": "<project>",
      "query": "<query>"
    },
    "name": "search_phrases"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesText to find in keys or values, case-insensitive, 1 to 200 characters
projectYesProject name; an id matches nothing
languageNoOnly search this locale code; every language when absent

Output Schema

NameRequiredDescriptionDefault
statusYes
phrasesYesUp to 100 matching phrases, values cut to 2,000 characters; phraseCount has the total
phraseCountYes
phrasesTruncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Restrict search to a specific language code (e.g. en, it)"New value: +"Only search this locale code; every language when absent"
    • changedInput schema / properties / project / description
      Previous value: -"Project name (slug) to search phrases in"New value: +"Project name; an id matches nothing"
    • changedInput schema / properties / query / description
      Previous value: -"Search text to match against phrase keys and values"New value: +"Text to find in keys or values, case-insensitive, 1 to 200 characters"
    • addedOutput schema / properties / phrases / description
      Added value: +"Up to 100 matching phrases, values cut to 2,000 characters; phraseCount has the total"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely useful behavior beyond that: a hard cap of 100 matches and the fact that matching is case-insensitive and confined to one project.

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, no wasted words, and the trigger plus scope are front-loaded ahead of the exclusion. Every clause carries information an agent needs.

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 an output schema present, return-value detail is optional, yet the description still conveys the match cap and project scoping. Nothing an agent needs in order to call this correctly is missing.

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 query, project and language semantics (case-insensitive, locale restriction, id does not match) are already fully documented in the schema. The description adds no syntax or format detail beyond it, so the 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 (find/search) and resource (translation strings by key or text content) and carves out its scope with 'Not for one exact key', which separates it from get_phrase. An agent can select this without opening the schema.

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 an explicit trigger ('Use this when someone asks to find translation strings that contain a word or phrase') and an exclusion ('Not for one exact key'). The alternative tool (get_phrase) is implied rather than named, so it falls just short of a 5.

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

All Multilocale Translations toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources