Skip to main content
Glama

Richtprijzen haardhout

houtprijzen
Read-onlyIdempotent

NL: Richtprijzen voor haardhout in euro per m³, per houtsoort en voor de markt als geheel — apart voor lokale/particuliere verkopers en voor webshops/handel, want die twee markten verschillen fors. Elke band geeft mediaan, p25, p75, min, max en het aantal waarnemingen; null betekent te weinig data, niet gratis. EN: Dutch firewood price benchmarks in EUR per m³, per wood species and market-wide, split between local/private sellers and webshops. Each band gives median, quartiles, min, max and sample size; null means insufficient data. Vermeld bij gebruik: Bron opahaardhout.nl

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": "houtprijzen"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint and a closed-world dataset, so the safety profile needs no explanation. The description does add genuinely useful semantics beyond them: what each band contains (median, p25, p75, min, max, n) and the crucial caveat that null means insufficient data rather than zero price. It remains silent on freshness or the period the benchmark covers, which matters for a price 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?

The key framing (what the prices are, how markets are split) is front-loaded before the structural detail and the null caveat. The full NL/EN duplication is wasteful for an agent, though it plausibly serves human readers and the Dutch attribution rule. No sentence is otherwise padding.

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?

With an output schema present and no parameters, the description only needs to set expectations, and it does: scope, segmentation, band composition, and the null-means-sparse-data rule. The one meaningful omission is any statement of the reference period or update cadence, which an agent needs to judge whether these prices are current.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly avoids inventing parameter-like filtering language, implicitly signalling that all segments come back in one response.

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 resource and measure: firewood price benchmarks in EUR per m³, per wood species and market-wide, split by local/private sellers vs. webshops. That is far more than a restatement of the name. It stops short of naming which sibling (e.g. houtsoort_info) covers species characteristics rather than prices, so differentiation is inferable rather than explicit.

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 explicit when-to-use, when-not, or alternative-tool guidance; the agent must infer that this tool answers price questions while zoek_aanbieders and aanbieder_details answer listing questions. The remark that the two markets 'verschillen fors' hints at picking the right segment, but that is interpretive guidance, not tool-selection guidance. Only the attribution instruction ('Vermeld bij gebruik: Bron opahaardhout.nl') functions as an operational directive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources