Skip to main content
Glama

translate_term

Read-only

Retrieve the official equivalent of an administrative term in another national language. Returns preferred designation and accepted variants for authority names, department titles, and legal acts.

Instructions

Get the official equivalent of an administrative term in another national language.

Returns the preferred designation (sequence 1) plus accepted variants, per matching entry. Use this for authority names, department titles and titles of legal acts.

Matches only against designation fields, so a term merely mentioned in a definition is never reported as an equivalent. term accepts Lucene wildcards; on an empty result retry with term* before concluding there is no equivalent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYes
max_resultsNo
to_languageNoFR
from_languageNoDE

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hitsYes
termYes
sourceNoData: TERMDAT, terminology database of the Swiss Federal Administration, Swiss Federal Chancellery (BK), via api.termdat.bk.admin.ch. The I14Y catalogue record carries no explicit licence statement — clarify terms with the Federal Chancellery before republishing.
provenanceYes
to_languageYes
retrieved_atYesISO-8601 UTC timestamp
from_languageYes
total_entriesYes
Behavior5/5

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

Beyond annotations (readOnly, openWorld, non-destructive), the description discloses critical behavioral details: matching only designation fields (not definitions), Lucene wildcard support, and the retry strategy. This adds significant value for correct invocation.

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?

The description is concise at 5 sentences, front-loaded with the main purpose, and efficiently conveys all necessary information without redundancy.

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?

Given the tool's moderate complexity, annotations, and presence of output schema, the description covers behavioral details, parameter hints, and usage context comprehensively. It leaves no obvious gaps for correct agent invocation.

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 coverage is 0%, so description must compensate. It explains the 'term' parameter accepts wildcards and suggests retry with 'term*'. However, 'max_results', 'to_language', and 'from_language' are not described beyond defaults in schema. The description adds some value but leaves key parameters underspecified.

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 clearly states the tool's purpose: 'Get the official equivalent of an administrative term in another national language.' It specifies the verb (Get), resource (equivalent), and scope (administrative term). It also distinguishes from siblings by focusing on translation of specific administrative terms.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context: 'Use this for authority names, department titles and titles of legal acts.' It also advises on retry strategy with Lucene wildcards. However, it does not explicitly contrast with sibling tools like search_terms or get_entries, leaving some ambiguity about when to use alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malkreide/termdat-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server