Skip to main content
Glama

Klusvang bouwmonitor: one closed month

bouwmonitor_month
Read-onlyIdempotent

The Klusvang bouwmonitor: a frozen monthly count of building-permit notices in the Netherlands, by work type and province, with a ranking of municipalities (optionally for one work type or one province). Without month: the latest closed month. Closed months never change. Counts only.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMunicipalities in the ranking. Default 20.
monthNoYYYY-MM. Default: the latest closed month.
provinceNoRank only the municipalities of this province.
work_typeNoRank municipalities by this work type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: the snapshot is frozen, closed months never change (so results are stable and safe to cache), and the payload is aggregate counts only, with no underlying notices.

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?

Four short sentences, front-loaded with the core definition and ending with the two most operationally important facts (default month, immutability). No filler. Slightly dense in the first sentence, which packs the full breakdown and ranking into one clause.

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 description effectively sketches the payload (counts by work type and province plus a municipality ranking), which matters given there is no output schema. However, it leaves open whether national and provincial totals are always returned when a filter is applied, and says nothing about ordering or size of the ranking beyond the schema's limit parameter.

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%, including enum values and the YYYY-MM pattern, so the schema does the heavy lifting. The description adds one nuance beyond the schema: province and work_type narrow the ranking rather than the headline counts. That is useful but marginal, so the baseline 3 is right.

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?

States a specific verb and resource: a frozen monthly count of building-permit notices in the Netherlands, broken down by work type and province with a municipality ranking. It is clear what the tool returns. It does not name the sibling tools (municipality_permit_counts, province_permit_counts, work_type_nationwide), so the agent must infer differentiation from the 'ranking of municipalities' framing alone.

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?

Usage is implied rather than stated: 'Without month: the latest closed month' tells the agent the default but not when to choose this tool over the per-province or per-municipality siblings. There is no explicit when-not guidance, though the emphasis on closed, immutable months signals a retrospective/reporting use case.

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