Skip to main content
Glama
simap MCP Server

simap MCP Server

by Digilac

Search BKP Codes

search_bkp_codes
Read-onlyIdempotent

Find the right Swiss BKP construction cost plan code by keyword or number for accurate cost classification.

Instructions

Search BKP (Swiss construction cost plan) 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_bkp_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, idempotentHint, openWorldHint and destructiveHint=false, so safety is fully covered. Beyond that the description only supplies the acronym expansion; it says nothing about whether matching is fuzzy or exact, whether the language parameter changes matching semantics, or how many results come back, which is the kind of behavior not visible in any structured field.

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 front-loaded sentence with zero filler, sized appropriately for a two-parameter lookup tool. It is tight rather than padded, though the brevity comes at the cost of the guidance noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool itself is simple and the schema is fully documented, but there is no output schema and the description says nothing about what a hit looks like (code, label, tree position) or the matching behavior. In a crowded family of parallel code-search tools, this leaves the agent without enough to choose confidently or interpret results.

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%: 'query' is documented as 'Search term (keyword or code number)' and 'lang' as 'Search language' with a de/fr/it/en enum. The description's 'by keyword or number' merely echoes the schema wording and adds no format, syntax or partial-match detail.

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?

The description gives a specific verb and resource (search BKP codes) and usefully expands the BKP acronym as the Swiss construction cost plan, which an agent cannot infer from the name alone. It does not, however, distinguish this from the sibling code searches (search_cpv_codes, search_npk_codes) or from browse_bkp_tree, which serves a related but different lookup path.

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 when-to-use or when-not-to-use guidance at all. With three sibling 'search_*_codes' tools and a 'browse_bkp_tree' tool exposed alongside this one, the description leaves the agent to infer that BKP applies to Swiss construction cost plans rather than CPV/NPK classification systems, and gives no hint about when browsing the tree is preferable.

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