Skip to main content
Glama
simap MCP Server

simap MCP Server

by Digilac

Search NPK Codes

search_npk_codes
Read-onlyIdempotent

Search standardized NPK position codes by keyword or number to locate matching codes for Swiss public tenders.

Instructions

Search NPK (standardized positions catalog) codes by keyword or 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_npk_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoSearch languageen
queryYesSearch term (keyword or code number)

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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond the annotations, such as result limits, pagination, language-dependent behavior, or whether it searches across all NPK levels.

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?

The definition is a single efficient sentence with no wasted wording, and the core action is front-loaded. It could be strengthened with one clause about choosing it over browse_npk_tree.

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 with rich annotations and fully described schema, the definition is minimally adequate. It omits what the search returns and does not explain when this search is preferable to browsing the NPK tree.

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 100%, so both query and lang are fully documented in the schema. The description reinforces that query can be a keyword or code number, but adds no meaning beyond the schema baseline.

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 NPK ... codes" and clarifies that NPK means "standardized positions catalog." It is clear what the tool does, though it does not distinguish itself from sibling code-search tools such as search_cpv_codes or browse_npk_tree.

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?

The description gives no explicit guidance on when to use this tool versus alternatives like browse_npk_tree or the other search_*_codes tools. Usage is only implied by the word "Search."

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