agent-media-toolkit

translate

Translate text into target_lang (e.g. 'Spanish', 'ja').

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": {
      "text": "<text>",
      "target_lang": "<target_lang>"
    },
    "name": "translate"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes
`source_lang`	No
`target_lang`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 14, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It only states the action ('translate text') without mentioning any side effects, safety, authentication needs, or constraints. This is insufficient for an agent to understand the tool's impact.

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

Conciseness3/5

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

The description is a single short sentence, which is concise but overly minimal. It could incorporate more useful detail without becoming verbose. The structure is adequate but not optimized for agent comprehension.

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

Completeness2/5

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

Given the lack of output schema and annotations, the description should provide more context about return values, failure modes, or behavior. It only covers basic input, leaving the agent without enough information to handle the tool correctly in diverse scenarios.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description only adds an example for 'target_lang'. It fails to explain the 'text' parameter format or the 'source_lang' parameter (which has a default). The description adds minimal value over the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: translate text into a target language. It uses a specific verb and resource, and provides an example (e.g., 'Spanish', 'ja'). While it does not explicitly differentiate from siblings like 'summarize' or 'transcribe', the purpose is distinct enough for typical usage.

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?

The description gives a basic usage pattern (provide text and target_lang) and an example, but it lacks guidance on when not to use this tool or alternatives. With siblings like 'subtitles' and 'transcribe', the description should clarify when translation is preferred over these related operations.

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

All agent-media-toolkit 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.