Skip to main content
Glama

Look up an official code list (I14Y)

lookup_code_list
Read-only

Search I14Y Swiss code lists by code or text—such as NOGA classifications—to retrieve matching entries and identifiers.

Instructions

Search the entries of an official Swiss code list on I14Y by code or text, e.g. NOGA industry classification ({codelist: 'NOGA_CLASS', query: 'bank'} or {codelist: 'NOGA_CLASS', query: '6419'}), NOGA levels NOGA_SECTION/NOGA_DIVISION/NOGA_GROUP/NOGA_CLASS/NOGA_TYPE, or any code list found with search_federal_metadata (pass its identifier or id).

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": {
      "codelist": "<codelist>",
      "query": "<query>"
    },
    "name": "lookup_code_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
limitNo
queryYesCode or words to search for
codelistYesCode list identifier (e.g. 'NOGA_CLASS') or concept id (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the external-read safety profile is covered. The description adds that the lookup hits I14Y and that a concept UUID is acceptable, but says nothing about response shape (code/label/level), result pagination, or behavior when a query matches many entries. Adequate but thin for a remote lookup with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence, front-loaded with purpose before the examples, with no filler. The parenthetical examples are long but each one demonstrates a distinct usage pattern (text query vs. code query, identifier vs. UUID).

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?

For a 4-parameter remote lookup with no output schema, the definition covers what to search and where to get identifiers, but omits what comes back and how partial/multiple matches behave. Nothing is misleading, but an agent cannot predict the response structure.

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 only 50%, and the description compensates for 'codelist' by enumerating concrete valid values (NOGA_CLASS, NOGA_SECTION/DIVISION/GROUP/TYPE) and clarifying that query accepts a numeric code as well as free text. However, 'lang' and 'limit' receive no mention in either the schema or the description, leaving a real gap.

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 plus resource: 'Search the entries of an official Swiss code list on I14Y by code or text'. The NOGA examples and the explicit pointer to search_federal_metadata for discovering other code lists make it distinguishable from the sibling list tools, which are largely fixed-catalog listings.

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?

Gives clear usage: search by code or by text, and tells the agent to obtain a codelist identifier or UUID via search_federal_metadata when the target list is not one of the NOGA ones. No explicit 'when not to use' or guidance on when to prefer a sibling list tool, but the context is unambiguous.

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