Skip to main content
Glama

Languages this can translate

translate.languages
Read-only

Use this when you need to know which languages and how much text the Ghana translation tool handles before calling it. Do not use it to translate: use translate.text for that.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "translate.languages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
byYes
pairsYes
cautionYes
max_charactersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered; the description adds the meaningful workflow context that this is a pre-flight check before calling the translation tool. It does not discuss caching, freshness, or scope limits of the returned list, but with an output schema present those details are less critical.

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?

Two short sentences, front-loaded with the positive use case followed by the exclusion and the sibling redirect. Every clause carries routing value and nothing is wasted.

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 zero-parameter, read-only discovery tool with an output schema, the description supplies what matters: what is returned and that it should precede translate.text. Minor gaps like whether the limits are per-request or per-total are tolerable given the output schema.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. It correctly signals that no inputs are needed to obtain the language list.

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 states a specific resource (the languages and text-size limits the Ghana translation tool handles) and names it distinctly from the sibling translate.text. It is clear what an agent gets back, though the phrasing 'how much text the tool handles' is slightly indirect compared with saying 'supported languages and input size limits'.

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?

It gives an explicit trigger ('Use this when you need to know which languages and how much text...') plus an explicit exclusion and redirect ('Do not use it to translate: use translate.text for that'). No inference is required to pick between the two tools.

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.

Resources