Skip to main content
Glama
simap MCP Server

simap MCP Server

by Digilac

Browse CPV Tree

browse_cpv_tree
Read-onlyIdempotent

Browse the CPV code hierarchy to display subcategories of a parent code, or list root categories when no parent code is specified.

Instructions

Browse the CPV code hierarchy (shows subcategories of a parent code)

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

Input Schema

NameRequiredDescriptionDefault
langNoDisplay languageen
parentCodeNoParent code (8 digits). 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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds only that it reveals subcategories, without stating traversal depth (one level vs. full subtree), result shape, or language-dependent output behavior.

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 no filler. It is efficient, though the terse phrasing leaves behavioral and usage gaps that could have been filled with one more sentence.

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?

This is a simple, read-only, two-optional-parameter tool with fully documented schema, so little is required. Still, with no output schema, the description should clarify what a browse result looks like (child codes and labels, depth, pagination), which it does not.

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%: the schema already documents the 8-digit parentCode pattern, the root-category behavior when omitted, and the lang enum with default. The description adds no further parameter meaning, so the baseline 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?

The description names a specific verb (browse) and resource (CPV code hierarchy) and clarifies the operation with 'shows subcategories of a parent code.' It implicitly distinguishes itself from search_cpv_codes by framing this as hierarchy traversal rather than lookup, though it does not name the sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical hints at when the tool is appropriate (exploring children of a known parent code), and the schema notes that omitting parentCode yields root categories. However, there is no explicit guidance on choosing this over search_cpv_codes or the other browse_*_tree tools.

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