Skip to main content
Glama
simap MCP Server

simap MCP Server

by Digilac

Search CPV Codes

search_cpv_codes
Read-onlyIdempotent

Search Common Procurement Vocabulary (CPV) codes by keyword or partial code number to identify the right procurement classification for tenders.

Instructions

Search CPV (Common Procurement Vocabulary) codes by keyword or partial code number

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
langNoSearch languageen
queryYesSearch term (keyword or code prefix)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.3.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the useful behavioral detail that matching is by keyword substring or code prefix, but says nothing about result limits, ranking, or how `lang` affects matches.

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?

A single, front-loaded sentence with no wasted wording; the acronym expansion and the two matching modes are packed in efficiently.

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 simple two-parameter search tool this covers the essentials, but with no output schema the description leaves the return shape unexplained (code plus label? flat list? ranked?), and it offers no routing advice against the many sibling code-search and browse tools.

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 100%, so the baseline is 3. The description does clarify that `query` behaves as a keyword or code-prefix match, which reinforces the schema wording, but it adds no information about the `lang` parameter or the consequences of choosing a non-English language.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search CPV ... codes') and expands the CPV acronym, and it names both matching modes (keyword or partial code number). It does not, however, distinguish this from the very similar siblings search_bkp_codes, search_npk_codes, search_oag_codes, or browse_cpv_tree, so the agent must infer the distinction from the tool name alone.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance: nothing says when to prefer this over browse_cpv_tree (hierarchical lookup) or over the other code-search siblings. Usage is only implied by the tool name and the description's mention of keyword/prefix searching.

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