Skip to main content
Glama
Digilac

simap MCP Server

by Digilac

browse_bkp_tree

Navigate the Swiss construction cost plan (BKP) hierarchy to locate and retrieve cost category codes for tender classification.

Instructions

Browse the BKP code hierarchy (Swiss construction cost plan)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parentCodeNoParent BKP code. If omitted, shows root categories
langNoDisplay languageen
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only states 'Browse', which implies a read-only operation, but offers no details on behavior (e.g., tree depth, pagination, or output format).

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, concise sentence that is front-loaded with the key action and resource. No unnecessary words or details.

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 browsing tool with 2 parameters and no output schema, the description covers the core purpose but lacks details about the hierarchy presentation (e.g., depth, recursion). Adequate but not complete.

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%, with each parameter already described in the input schema. The description adds no additional meaning beyond what's in the schema, so baseline 3 is appropriate.

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?

The description clearly states the action ('Browse') and the resource ('BKP code hierarchy') with context ('Swiss construction cost plan'). This distinguishes it from sibling tools for other code hierarchies (CPV, NPK, OAG).

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?

The description implies usage for navigating the BKP hierarchy, and sibling tool names make the alternative contexts clear. However, no explicit when-to-use or when-not-to-use guidance is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Digilac/simap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server