Skip to main content
Glama
simap MCP Server

simap MCP Server

by Digilac

Browse BKP Tree

browse_bkp_tree
Read-onlyIdempotent

Browse the Swiss BKP construction cost plan hierarchy by parent code and display language to locate root or child cost categories.

Instructions

Browse the BKP code hierarchy (Swiss construction cost plan)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse_bkp_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoDisplay languageen
parentCodeNoParent BKP code. If omitted, shows root categories

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered and the description need not repeat it. The description adds domain context (Swiss construction cost plan) but says nothing about what a browse returns, tree depth, or whether the hierarchy is lazy-loaded per parentCode — useful behavioral detail that is missing.

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 short sentence, front-loaded with the verb and resource, with zero redundant wording. It is efficient, though its brevity leaves the gaps noted in the other dimensions rather than being a structuring flaw.

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 two-parameter, optional-args, read-only tree browser with full schema coverage and four annotation hints, the definition covers what the tool is. The residual gap is that no output schema exists and the description does not say what a browse result looks like, but the tool's simplicity keeps this a minor omission.

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%, with both parameters documented in the schema itself (lang as display language with enum, parentCode with pattern and root-category default). The description contributes no additional parameter meaning, so the baseline of 3 applies.

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: 'Browse the BKP code hierarchy', with a parenthetical identifying the domain ('Swiss construction cost plan'). It is clear what the tool does, but it never distinguishes itself from the several sibling tree browsers (browse_oag_tree, browse_cpv_tree, browse_npk_tree) or from search_bkp_codes, so an agent must infer the difference from names 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 when-to-use or when-not-to-use guidance: nothing says to pick this over search_bkp_codes when looking up codes, or over the other browse_*_tree tools for other classification systems. The only usage hint lives in the schema ('If omitted, shows root categories'), not the description.

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