Skip to main content
Glama
Sign In
Tapra MCP server

Tapra MCP server

Official
by tapra-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Translation languages

list_translation_languages
Read-onlyIdempotent

Retrieve the free list of source and target languages accepted by translation to choose valid language codes before sending a request.

Instructions

List the languages translate accepts as source and target. Free.

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": "list_translation_languages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds one genuinely new fact beyond them: the call is free, which matters for an agent deciding whether to look up languages liberally rather than caching or guessing. It omits any note on result size or caching, keeping it short of a 5.

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 clauses, zero waste, with the scope statement first and the cost hint second. Nothing is buried or redundant.

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

Completeness3/5

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

The tool has no output schema, and the description never indicates the shape of the response — whether it returns language codes, display names, or source/target pairs. An agent that must feed a value into `translate` is left to discover the format by calling it. Otherwise adequate for a trivial parameterless lookup.

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 there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The sentence correctly signals that no filtering or arguments are needed to scope the list.

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?

Specific verb (list) plus a precisely scoped resource (the languages translate accepts as source and target), which ties the tool to the sibling `translate` rather than leaving it ambiguous against `list_voices` or the other list-style lookups. An agent can select it without opening any schema.

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?

Mentioning that these are the languages `translate` accepts implies the tool is a prerequisite lookup before calling `translate`, but the implicit routing is never stated as such and no exclusions or sequencing guidance is given. Usage is inferable rather than spelled out.

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

Deploy Server

Other Tools