Skip to main content
Glama
Sign In

EaseWeb

by host.easeweb
OverviewDiscussionsAdmin

Translate what is not translated

translate_presentation

Fill in, by machine translation, the texts of a presentation you may edit that have no translation into the other languages of the site yet: the title, the slide names and the texts of text, shape and button blocks. Translations a person or an agent wrote stay as they are; machine translations whose source text changed are made again. The site does this by itself a few seconds after every change when it has a translator; this does it now and says how many. Answers 503 when the site has no translator.

Input Schema

NameRequiredDescriptionDefault
slugYesThe presentation's slug (its address: /movie/<slug>/).

Output Schema

NameRequiredDescriptionDefault
translatedYesTranslations made now.
missing_translationsNoWhat is not translated yet into the other languages of the site (add it): the first ones; "missing_translations_count" says how many there are.
missing_translations_countNoHow many texts are not translated yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / missing_translations / items / properties / outdated
      Added value: +{
+  "description": "There is a translation, written for an earlier text.",
+  "type": "boolean"
+}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses exactly what gets mutated (only missing/changed machine translations), what is preserved, that it reports a count, and that it returns 503 when no translator is configured. This is rich behavioral context an agent needs before invoking a write operation.

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?

Front-loads the verb and scope, and every clause carries information (scope, preservation rules, retranslation rule, auto-vs-now timing, error code). The sentences are dense and slightly run-on but not padded.

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?

Even with an output schema present, it notes the count returned and the 503 failure mode, covering mutation scope and error behavior. For a single-param tool with full schema coverage, nothing material 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?

Only one parameter and the schema already documents it at 100% coverage (slug, with the /movie/<slug>/ form). The description adds no further parameter detail, so the 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 action (fill in machine translations) on a specific resource (presentation texts) and enumerates the exact scope: title, slide names, and text/shape/button block texts. It also clarifies what is outside scope (human/agent translations stay, unchanged-source machine translations stay), making the operation unambiguous.

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

Usage Guidelines4/5

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

Explains the site auto-translates a few seconds after each change when a translator exists, implying this tool is for translating immediately rather than waiting. It doesn't give explicit 'use this instead of X' routing, but no sibling performs translation, and the immediate-vs-deferred condition is clear.

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

All EaseWeb 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