Skip to main content
Glama

Tolgee

by io.github.tolgee

create_keys

Create translation keys in a Tolgee project with optional translations and tags. Keys that already exist are silently skipped — their translations and tags are not updated. Use update_key and set_translation to modify existing keys.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keysYesList of keys to create
branchNoOptional: branch name
namespaceNoOptional: default namespace for all keys (individual keys can override)
projectIdNoID of the project (required for PAT, auto-resolved for PAK)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the critical behavior that existing keys are silently skipped and their translations/tags are not updated. It also directs users to update tools. It doesn't mention authentication or error scenarios, but these are partially covered in the schema (e.g., projectId requirement).

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 purpose and followed by vital behavioral context and alternative tools. Every word earns its place with no redundancy or fluff.

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

Completeness4/5

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

For a creation tool with 4 parameters fully documented in the schema, the description covers the essential behavior (skip existing keys) and provides guidance for alternative tools. It doesn't describe return values, but no output schema exists. The description is sufficient for selection and invocation, though it could mention the branch/namespace options for full completeness.

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 description coverage is 100%, so the baseline is 3. The description mentions optional translations and tags, which aligns with the schema, but adds no extra parameter semantics beyond what the schema already provides. The skip behavior is not a parameter detail.

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 creates translation keys in a Tolgee project with optional translations and tags. It distinguishes itself from sibling tools by explicitly naming update_key and set_translation as alternatives for modifying existing keys.

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

Usage Guidelines5/5

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

It explicitly says when to use this tool (to create keys) and when not to (keys that already exist are skipped). It names specific alternative tools for modifying existing keys, providing clear decision guidance.

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

All Tolgee toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness3/5

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.

Resources