Skip to main content
Glama

delete_translation_language

DestructiveIdempotent

Permanently remove a survey language and every translation in it, with confirm: true. Cannot be undone.

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": {
      "survey_id": "<survey_id>",
      "code": "<code>",
      "confirm": "<confirm>"
    },
    "name": "delete_translation_language"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesLanguage code to remove (from read_translation)
confirmYesMust be true. Every translation in that language is deleted and cannot be recovered.
survey_idYesSurvey UUID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is given; the description still adds the cascade behavior ('every translation in it') and irreversibility ('Cannot be undone'), which is meaningful context beyond the structured fields. It omits any note on auth/permission requirements or side effects on survey versions, so it stops short of full disclosure.

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 short sentences, zero filler, with the destructive nature and the confirm requirement front-loaded. Every clause carries information the agent needs before calling.

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?

With an output schema present, return values need not be explained, and all three required parameters are covered. The description conveys irreversibility and cascade scope, though it leaves open edge cases such as deleting a survey's primary/default language.

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 coverage is 100% and all three parameters are already documented in the schema, so the baseline applies. The description reinforces the confirm=true requirement and conveys the consequence of that flag, but adds no syntax or format detail for survey_id or code beyond what the schema provides.

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 gives a specific verb ('Permanently remove') and resource ('a survey language and every translation in it'), and the scope of what is removed (the language plus all its translations) cleanly separates it from edit_translation and read_translation. An agent can tell what this tool does without opening the schema.

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

Usage Guidelines3/5

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

It states the required precondition ('with confirm: true'), which is real usage guidance, but it never says when to choose this over edit_translation or when not to delete a language (e.g., the survey's default/base language). Usage is implied rather than framed against alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources