Skip to main content
Glama

create_key

Add a new localization key to a Tolgee project with optional namespace and initial translations.

Instructions

Create a new localization key in a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    name: The key name (e.g., "button.submit", "greeting.hello").
    namespace: Optional namespace for the key.
    translations: Optional dict mapping language tags to translation values (e.g., {"en": "Hello", "fr": "Bonjour"}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
nameYes
namespaceNo
translationsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains the optional namespace and translations parameters, including an example for translations. However, it does not disclose key creation behavior (e.g., whether duplicate keys are rejected, permissions needed, or side effects).

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?

The description is concise and well-structured, with a clear purpose statement followed by parameter documentation in a typical Args format. No extraneous information; every sentence adds value.

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

Completeness3/5

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

Given the complexity of 4 parameters and no annotations, the description covers parameter semantics well but lacks usage guidelines and behavioral context (e.g., error conditions, idempotency). The presence of an output schema partially compensates for return value information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must add meaning. It does so effectively by explaining each parameter: project_id is numeric names with examples, namespace is optional, translations is an optional dict mapping language tags to values. This adds significant value beyond the schema's type info.

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?

The description clearly states the tool's purpose: 'Create a new localization key in a Tolgee project.' It specifies the verb 'create' and the resource 'localization key', distinguishing it from sibling tools like create_language or delete_keys.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool vs alternatives. It does not mention prerequisites, when to prefer create_key over update_key or import_keys, or any workflow context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ytarfa/tolgee-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server