Skip to main content
Glama

search_terms

Read-only

Look up officially validated designations of Swiss federal authorities, departments, and legal acts in DE/FR/IT/EN from the TERMDAT database.

Instructions

Search TERMDAT for official designations of the Swiss Federal Administration.

Use this to look up the officially validated German/French/Italian/English name of an authority, department or legal act — for example to check how a body is named in another national language before citing it.

search_term is Lucene query syntax: * and ? wildcards and the ~ fuzzy operator work. Matching is on whole words, so a compound is not found by its parts — «Quellensteuer» does not match «Quellensteuerverordnung», but «Quellensteuer*» does. Reach for a wildcard before concluding a term is absent.

out_language adds a target language to every entry's variants — it is purely additive and never filters the result set. fields is a comma-separated subset of: Terminus, Name, Abbreviation, Phraseology, Definition, Note, Context, Source, Metadata, Country, Comment; empty means Terminus, Name, Abbreviation, Phraseology, Definition, Note, Source. By default the search spans all 23 subject classifications; pass classification_ids or collection_ids to narrow it (see list_classifications / list_collections).

Scope caveat: TERMDAT holds administrative nomenclature (authority names, titles of legal acts, abbreviations), not domain vocabulary — so a term may genuinely be absent. Establish that with a wildcard retry, not from a single empty result, and never fill the gap with a guessed designation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detailNo
fieldsNo
in_languageNoDE
max_resultsNo
search_termYes
out_languageNo
collection_idsNo
classification_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNoSet when the search returned nothing; suggests how to widen it
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.
entriesYes
returnedYes
truncatedYesTrue if the result hit max_results — narrow the query or raise the limit
provenanceYes
in_languageYes
search_termYes
out_languageNo
retrieved_atYesISO-8601 UTC timestamp
Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint, destructiveHint), the description explains Lucene query syntax, whole-word matching, additive nature of out_language, default fields, and the concept of absent terms. It advises wildcards to avoid false negatives.

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 well-structured: purpose sentence, usage guidelines, parameter details, then scope caveat. Every sentence is informative and non-redundant, fitting all necessary information without verbosity.

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 complexity (8 parameters, search semantics) and the presence of an output schema, the description covers essential aspects: purpose, usage, parameter behavior, and limitations. It provides sufficient context for correct invocation.

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?

With 0% schema description coverage, the description explains search_term (Lucene, wildcards), out_language (additive), fields (comma-separated list), and classification/collection_ids (narrowing). However, detail and in_language parameters are not explained beyond defaults.

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 searches TERMDAT for official designations of Swiss Federal Administration. It specifies the resource and verb, and distinguishes from siblings by explaining the administrative scope and referencing list_classifications/list_collections for narrowing.

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?

The description provides explicit when-to-use guidance (e.g., look up official names before citing), when-not-to (not for domain vocabulary), and alternatives (retry with wildcard, use list_* for classifications). It also cautions against filling gaps with guessed designations.

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