RooQuiz

Update form translation

update_form_translation

Destructive

Save translated copy for one language version of a form. Pass the translated title / description / fields / report / systemText / booking, mirroring the shape returned by get_form_translation; fields you omit keep their current value and partial translation is allowed. Translation fields[] must not introduce codes that do not exist on the source form. Pass isActive=false to pause just this language version, independently of the form's overall isActive.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	No	Translated form title
`fields`	No	Translated questions mirroring the source structure: same codes, translated text. The current draft comes from get_form_translation (or the clone create_form_translation returns) — edit the text in place and send it back. Merging is by code, not position, so a partial list is fine and omitted questions stay untranslated.
`formId`	Yes	The source form UUID
`report`	No	Translated report display text, mirroring the stored report that get_form_translation returns — the nested overallAnalysis / dimensionAnalysis / outcomeAnalysis shape, NOT the flattened `report` input of create_form / update_form. Scores, formulas, thresholds and codes always come from the source; only the text keys below are applied.
`booking`	No	Translated copy for the result-page booking block (the block that offers a call). Whether the block shows at all always comes from the source form — this only translates its wording. Omit a key or send it empty to keep falling back to the source text.
`isActive`	No	Enable/pause this language version (independent of the form's overall isActive).
`language`	Yes	Which language version to update
`systemText`	No	Translated answer-page system copy, as an open key→text map (e.g. { "submitButton": "Absenden", "nextPage": "Weiter" }). Keys are the answer-page copy keys — read the ones already set from get_form_translation, and note that keys the answer page does not know are stored but never rendered. Every key is optional; an empty value falls back to the built-in text for this language.
`description`	No	Translated form description

Output Schema

TableJSON Schema

Name	Required	Description
`formId`	No	The source form
`updated`	No	Which parts of the translation this call changed
`language`	No	Language that was saved

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 29, 2026

addedInput schema / properties / fields / items / properties / explain

Added value: +{
+  "description": "Knowledge quiz: translated answer explanation shown in the answer review.",
+  "type": "string"
+}

added

Input schema / properties / report / properties / dimensionAnalysis / properties / dimensions / items / properties / levels / items / properties / cta

Added value: +{
+  "additionalProperties": true,
+  "description": "Only the CTA button text is translatable; the link and its settings come from the source.",
+  "properties": {
+    "text": {
+      "description": "Translated CTA button text.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / report / properties / overallAnalysis / properties / levels / items / properties / cta

Added value: +{
+  "additionalProperties": true,
+  "description": "Only the CTA button text is translatable; the link and its settings come from the source.",
+  "properties": {
+    "text": {
+      "description": "Translated CTA button text.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedAug 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: partial translation is allowed, omitted fields keep their current values, fields[] must not introduce unknown codes, and isActive=false pauses only this language version independently of the form's isActive. These details clarify the mutation and merge behavior that readOnlyHint/destructiveHint alone do not convey.

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 a tight set of four sentences with no filler. Each sentence earns its place: the main action, the mirroring/merge behavior, the code validation constraint, and the isActive override. The most important operational guidance is front-loaded.

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

Completeness5/5

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

For a complex tool with 9 parameters and deeply nested objects, the description plus schema is highly complete. It gives the critical workflow hint (start from get_form_translation), covers partial updates, validation constraints, and the isActive edge case, while the output schema covers return value expectations.

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

Parameters4/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, but the description adds valuable cross-parameter meaning: it tells the agent to mirror get_form_translation's shape, clarifies that omitted fields retain current values, and explains that codes must exist on the source form. This goes beyond the per-property schema documentation and meaningfully helps an agent construct a valid payload.

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 opens with a specific verb-resource pair, 'Save translated copy for one language version of a form,' which clearly states what the tool does and its scope. It distinguishes itself from related translation tools like create_form_translation by emphasizing update semantics such as preserving omitted fields.

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?

The description gives clear context that this updates an existing language version and references get_form_translation as the source of the shape to mirror. However, it never explicitly says when to use this over create_form_translation or other translation-related siblings, so the when-not-to-use guidance is only implied rather than stated.

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

All RooQuiz tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?