Skip to main content
Glama
simap MCP Server

simap MCP Server

by Digilac

Browse NPK Tree

browse_npk_tree
Read-onlyIdempotent

Browse the NPK code hierarchy to navigate standardized position categories for Swiss tenders, viewing root categories or child codes by parent code and language.

Instructions

Browse the NPK code hierarchy (standardized positions catalog)

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_npk_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoDisplay languageen
parentCodeNoParent NPK 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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds essentially no behavior beyond them: it does not say whether a call returns a single level of children or a full recursive subtree, nor how deep the hierarchy goes — the most consequential ambiguity for a tree-browsing tool.

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 compact sentence with no filler, front-loaded with the verb and resource. It is efficient, though the brevity borders on under-specification rather than disciplined concision.

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?

The tool is simple — two optional parameters, no output schema, and rich annotations — so a short description is defensible. The missing piece is the shape of the result (one level vs. subtree) and how it relates to the sibling search tools, which leaves the agent guessing on invocation strategy.

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 'parentCode' documented as 'Parent NPK code. If omitted, shows root categories' and 'lang' as display language, so the schema carries the parameter burden. The description adds no additional meaning, which is acceptable at full coverage but earns only the 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?

The description pairs the verb 'Browse' with a specific resource, 'the NPK code hierarchy', and adds a parenthetical gloss ('standardized positions catalog') that tells the agent what NPK codes represent. It is clear on its own, but it never contrasts itself with the sibling 'search_npk_codes', so the browse-vs-search distinction is left to inference.

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 guidance, no stated prerequisites, and no named alternative. The agent must infer from the name alone whether to browse the tree or call search_npk_codes / search_bkp_codes, and nothing in the description helps make that choice.

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