Skip to main content
Glama
Sign In

Youform

by io.github.mkmaker
OverviewDiscussionsAdmin

Get translation

get-translation-tool
Read-only

Get a form's translatable strings: source_messages holds every translatable string in the form's default language (system messages + per-block field messages), and translated_content holds the current translation for the requested language (null if that language has not been added yet). Use this before update-translation-tool — the translated_content you send back must mirror the structure of source_messages.

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": {
      "form_slug": "<form_slug>",
      "language": "<language>"
    },
    "name": "get-translation-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageYesLanguage code of the translation to fetch, e.g. "de", "fr", "zh-cn", "pt-br". Existing translations are listed by get-form-tool.
form_slugYesThe form's slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine non-obvious behavior — translated_content is null rather than an error when the language hasn't been added yet, and source_messages mixes system messages with per-block field messages. It does not say what happens with an invalid form_slug or unsupported language code, a minor remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the purpose and the two return fields, then the sequencing rule. The first sentence is dense and long with nested parentheticals, but every clause carries usable information and nothing is filler.

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?

There is no output schema, so the description must carry the return shape — and it does, naming both top-level fields, their contents, and the null case. Combined with annotations covering the read-only profile, nothing an agent needs to call this correctly and chain into update-translation-tool is missing.

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 both parameters are already documented, including example language codes and the pointer to get-form-tool for listing existing translations. The description adds nothing further about form_slug or language format; its detail is about return values rather than parameter semantics. Baseline 3 applies.

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?

States a specific verb and resource ("Get a form's translatable strings") and immediately names the two return fields, source_messages and translated_content, with their meaning. An agent can distinguish it from get-form-tool and update-translation-tool without opening any schema.

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?

Explicitly prescribes the workflow: "Use this before update-translation-tool" and explains the constraint that translated_content must mirror source_messages' structure. The downstream alternative and the condition that selects it are both stated outright.

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

All Youform toolsInspect
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