get_projectFetch a single MultiLocale project by id or name. Returns bounded Markdown and structured project metadata, including name, configured locales, and timestamps.
| Name | Required | Description | Default |
|---|---|---|---|
| projectIdOrName | Yes | Project id or project name (slug) |
| Name | Required | Description | Default |
|---|---|---|---|
| status | Yes | ||
| project | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive, so no side-effect disclosure is needed. Description adds output specifics ('bounded Markdown', fields), which is mild context, but no auth or rate-limit behavior is addressed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences, front-loaded with action and identifier, no fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter read-only tool with a full schema and rich annotations, the description covers what it does and what it returns; nothing needed to invoke it is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of the one parameter, including meaning (id or slug) and maxLength. Description merely repeats 'by id or name', adding no extra semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Fetch) and resource (single MultiLocale project) with id or name. The word 'single' distinguishes it from list_projects, though it doesn't name show_project_overview, so it doesn't fully separate it from all siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies use when you need one project identified by id or name, but gives no explicit when-not or alternative guidance such as show_project_overview or list_projects. The context is inferable but not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but several overlap: get_project and show_project_overview both fetch a project by id/name, and list_phrases, search_phrases, and export_locale_dictionary all return phrase collections in similar ways. Descriptions help clarify edge cases, but an agent could plausibly select the wrong tool in several scenarios.
All tool names follow a consistent snake_case verb_noun pattern: add_, delete_, get_, list_, search_, find_, update_, export_, share_, show_. Minor differences like get_project vs show_project_overview do not break the overall naming convention.
17 tools is slightly above the ideal range but still reasonable for a localization server covering projects, locales, phrases, translation searches, sharing, and team roster. Each tool represents a real operation, even if a few could be consolidated.
The surface covers core project and phrase lifecycles well: create/read/update for projects and phrases, delete for phrases, locale updates, translation generation, search/export, and missing-translation analysis. Minor gaps exist, such as no delete_project, no explicit unshare_phrase operation, and no dedicated remove_locale tool.