Skip to main content
Glama

translate

Read-onlyIdempotent

Translate text to any language with tone control (formal/casual/technical). Auto-detects source language. Preserves formatting and cultural nuances. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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>",
      "targetLanguage": "<targetLanguage>"
    },
    "name": "translate"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to translate
toneNoTranslation toneformal
sourceLanguageNoSource language (auto-detected if omitted)
targetLanguageYesTarget language (e.g., Spanish, French, Japanese)

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 readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: automatic source-language detection, formatting/cultural-nuance preservation, and — most valuably — a quota behavior where after 10 free calls per day the response changes shape to an x402 pay-per-call endpoint plus price. That last detail materially affects how an agent should interpret a result, though the exact payload on quota exhaustion is not fully spelled out.

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?

Three tight sentences, front-loaded with the core action, each carrying distinct information (capability, detection/formatting behavior, quota/pricing). No filler or restated title.

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?

For a 4-parameter tool with full schema coverage and no output schema, the description covers capability, defaults, detection, and quota behavior well. The remaining gap is the return shape — it does not say explicitly that the tool returns the translated string (or how quota-exhausted responses are distinguished from successful ones), which matters since no output schema exists.

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 every parameter is already documented with types, enums, defaults, and constraints. The description echoes the tone options and auto-detection behavior already stated in the schema but adds no syntax, format, or edge-case detail (e.g., accepted language names/codes) beyond it. Baseline 3 is appropriate.

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 and resource ('Translate text to any language') and immediately scopes the capability with tone control and auto-detection. No sibling tool in the list does translation, so an agent can identify this as the text-translation tool without ambiguity.

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?

Usage is only implied — the description makes clear this is the tool for translating arbitrary text, but it gives no explicit when-to-use/when-not guidance or alternatives (there are none among siblings, which limits how much is needed). The free-tier note hints at a call-budget consideration but is framed as pricing, not invocation guidance.

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.