Skip to main content
Glama
simap MCP Server

simap MCP Server

by Digilac

Browse OAG Tree

browse_oag_tree
Read-onlyIdempotent

Browse the OAG code hierarchy to locate object type classifications for Swiss public tenders; use optional parent code and language filters to narrow results.

Instructions

Browse the OAG code hierarchy (object type classification)

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

Input Schema

NameRequiredDescriptionDefault
langNoDisplay languageen
parentCodeNoParent OAG 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 this as a safe, read-only, idempotent, open-world operation. The description adds only that the hierarchy represents object type classification, without describing return format, pagination, language behavior, or traversal behavior, so it provides modest additional context beyond the annotations.

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?

The description is a single front-loaded sentence with no wasted wording. It is concise, though its brevity leaves no structured detail about navigation or usage.

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 two-parameter browsing tool with full schema coverage and annotations covering safety, the definition is minimally adequate. However, it does not explain what browsing returns, how parentCode drives traversal, or how this differs from sibling search tools, leaving gaps an agent must infer.

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?

The input schema has 100% description coverage, and it already explains that parentCode omitted shows root categories and that lang selects display language. The description adds no parameter meaning beyond the schema, so the baseline score 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?

The description states a specific verb and resource: browsing the OAG code hierarchy, clarified as object type classification. It is clear what the tool does, though it does not explicitly distinguish browsing from searching in sibling tools such as search_oag_codes.

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?

The description gives no explicit when-to-use guidance, no conditions for choosing this over search_oag_codes, and no mention of when browsing the hierarchy is preferable to searching codes directly. Usage is only implied by the tool name and the word 'Browse'.

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