Skip to main content
Glama

Find CPV procurement codes

search_cpv_codes
Read-only

Look up Common Procurement Vocabulary (CPV) codes by keyword or partial number, then use the 8-digit results to filter Swiss public tender searches.

Instructions

Look up Common Procurement Vocabulary (CPV) codes by keyword or partial number, e.g. 'Strassenbau', 'software', '4523'. Use the 8-digit codes as cpv_codes in search_public_tenders.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for titles and texts (falls back to the notice's original language)de
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), and the description adds the behavior that matters most: matching is fuzzy/prefix-based on keywords or partial numbers, and the output is identifier codes intended for reuse elsewhere. It does not mention page size behavior or whether the results include titles/descriptions, which is a minor remaining gap.

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 sentences, no waste: the purpose and input forms come first, followed by the handoff instruction. Examples are inline rather than in a separate block, which keeps it compact.

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 simple read-only lookup with no output schema, the description covers what the tool is, what inputs it takes, and how to use the result. Only the shape of a returned entry (code plus language-dependent title) is left implicit, and the `lang` parameter description in the schema partly covers that.

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 description coverage is only 33% — `lang` is documented, but `query` and `limit` are not. The description compensates for `query` by explaining that it accepts keywords or partial numbers and giving three concrete examples spanning German and English terms, but says nothing about `limit` or the default 30 results, which the agent must infer from the schema.

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?

Names a specific verb and resource ("Look up Common Procurement Vocabulary (CPV) codes") and pins down the accepted input forms with examples ('Strassenbau', 'software', '4523'). It also tells the agent what a successful result contains (8-digit codes), so it is unmistakable against siblings like search_public_tenders, which consume rather than produce these codes.

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?

Explicitly states the downstream workflow: take the 8-digit codes and pass them as `cpv_codes` to search_public_tenders. That is genuine when-to-use guidance linking two tools. It stops short of stating when not to use it (e.g. browsing the CPV tree by hierarchy without a keyword), but the intended context is clear.

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