tolgee-mcp

by ytarfa

Overview Schema Source Related Servers Discussions Admin

Python

Remote

update_project

Update a Tolgee project's name by providing its numeric ID and the new name.

Instructions

Update an existing Tolgee project's settings.

Args:
    project_id: The numeric ID of the project to update.
    name: The new name for the project.

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_id": "<project_id>",
      "name": "<name>"
    },
    "name": "update_project"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes
`name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 28, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations provided. The description only says 'update settings' but only mentions the name parameter, implying other settings may be involved. It does not disclose validation behavior, atomicity, 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?

Extremely concise: one sentence plus parameter list. Every word is necessary and front-loaded. No wasted space.

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 simple update tool with only two parameters and output schema available, the description covers purpose and parameter meanings. It is nearly complete, though could mention that only the name field is updatable.

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 0%, but the description adds meaning: 'numeric ID' for project_id and 'new name' for name. This is adequate but minimal.

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 'Update an existing Tolgee project's settings,' specifying the verb (update) and resource (project settings). It lists the two parameters, distinguishing it from create_project (creates new) and get_project (reads).

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?

No guidance on when to use this tool vs alternatives (e.g., create_project, delete_project). It does not specify prerequisites like needing the project ID or whether the project must already exist.

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