List all namespaces in a Tolgee project. Namespaces organize translation keys into logical groups (e.g. by feature, page, or module).
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | No | ID of the project (required for PAT, auto-resolved for PAK) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure. 'List' implies a read-only operation, but the description does not mention any additional behaviors such as pagination, sorting, or authentication requirements. It is adequate but lacks depth.
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?
The description is two sentences long, front-loaded with the action, and the second sentence adds useful domain context without redundancy. Every word contributes to understanding the tool's purpose.
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?
Given the low tool complexity (1 optional parameter, no output schema), the description sufficiently covers what the tool does and the context of namespaces. It could mention the return type implicitly, but 'List all namespaces' makes it obvious. The description is complete for the tool's simplicity.
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?
The schema provides 100% coverage for the single parameter (projectId) with a description. The tool description does not add any parameter details beyond what the schema already explains, so the baseline of 3 is appropriate.
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?
The description clearly states the tool's action ('List all namespaces') and the resource ('in a Tolgee project'), and it distinguishes itself from sibling list tools (list_branches, list_keys, list_languages, list_projects) by focusing on namespaces. The additional context about namespaces organizing translation keys adds clarity.
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?
The description implies the tool should be used when you need to see all namespaces in a project. It provides context about what namespaces are, but does not explicitly mention when not to use it or mention alternatives. For a simple listing tool, this is clear enough.
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 target distinct entities and actions, but a few pairs like create_keys/set_translation and list_keys/search_keys have overlapping functionality. The descriptions clearly differentiate their use cases, so ambiguity is limited.
All tools follow a consistent snake_case verb_noun pattern (create_, delete_, get_, list_, set_, etc.), making the API predictable. The only slight deviation is machine_translate, but it still reads as a single action verb.
With 22 tools, the server covers many aspects of translation management, but the count is slightly above the ideal range. Each tool has a clear purpose, though some could potentially be consolidated without loss of functionality.
The core key and translation lifecycle is well covered, but there are notable gaps: languages only support create and list (no update/delete), tags can be added but not removed, and projects lack get/update/delete operations. These omissions may require workarounds.
