Ghana Translate

Translate between English and Twi, Ewe or Ga

translate.text

Read-only

Use this when someone wants a short text translated between English and one of Twi, Ewe or Ga, three languages of Ghana: a greeting, a sign, a message to a relative, a line for a card. The text may be up to 300 characters and one side must be English. Do not use it for long documents, for legal, medical or other text where a mistake could cause harm, for names or passwords, or between two Ghanaian languages directly. The text is sent to the Khaya translation service.

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>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "translate.text"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	The language to translate into.
`from`	Yes	The language the text is in.
`text`	Yes	The text to translate.

Output Schema

Name	Required	Description	Default
`by`	Yes
`to`	Yes
`from`	Yes
`text`	Yes
`caution`	Yes
`explore_url`	No
`translation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly and non-destructive, so the description's job is to add operational context, and it does: the 300-character ceiling and the fact that text is sent to the third-party Khaya translation service (a privacy-relevant detail an agent would otherwise miss). It stops short of covering failure modes, quota, or what happens when the service is unavailable. The external-service disclosure sits slightly in tension with openWorldHint=false, but a fixed backend API call is not the open-ended interaction that hint usually governs, so this is not treated as a contradiction.

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?

Four sentences, front-loaded with the use case, then constraints, then exclusions, then a data-handling note. No sentence is redundant against another; each adds a distinct decision-relevant fact.

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?

An output schema exists, so return values need no explanation. For a three-parameter, single-service translation tool the description covers purpose, size limit, language-pair constraint, unsuitable inputs, and data destination, which is everything an agent needs to invoke it responsibly.

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 coverage is 100% and both enum parameters are self-describing, so the schema carries most of the burden. The description nonetheless adds a cross-field constraint the schema does not encode: the from/to pair is not free, one side must be English, even though the schema would accept twi-to-ewe. That is genuine added meaning beyond the structured fields.

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 ('short text translated between English and one of Twi, Ewe or Ga'), names the language set and constrains scope to short text, which cleanly separates it from the sibling translate.languages that would only enumerate languages. An agent can pick this tool without opening the 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?

Gives explicit when-to-use triggers ('a greeting, a sign, a message to a relative, a line for a card') and explicit when-not-to-use cases (long documents, legal or medical text, names or passwords, direct translation between two Ghanaian languages). The English-on-one-side precondition is stated as a routing rule, not left to inference.

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

All Ghana Translate 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?