Skip to main content
Glama

Permit counts for one municipality

municipality_permit_counts
Read-onlyIdempotent

How many building-permit notices (omgevingsvergunningen) one Dutch municipality published recently: the last 60 and 30 days, the 30 days before, new applications, recent grants, a breakdown by work type, and its total and national rank in the latest closed month of the Klusvang bouwmonitor. Counts only: no addresses, names or single permits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "municipality": "<municipality>"
    },
    "name": "municipality_permit_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_typeNoWork type, e.g. dakkapel (dormer), aanbouw (extension), kozijnen (window frames).
municipalityYesMunicipality URL slug, e.g. nijmegen or s-hertogenbosch. Use find_municipality to get it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld=false, so the safety profile is covered. The description adds substantive context beyond that: output is strictly aggregated counts with no addresses, names or individual permits, and the monthly figures come from the 'latest closed month', which tells the agent about data freshness. Return formatting and pagination are not a concern here because the tool returns a fixed metric set.

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 naming the resource first, then the metric list, ending with the aggregation caveat. Dense but every clause carries information the agent needs, since there is no output schema to describe the returned fields.

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 no output schema, the enumerated metric list effectively substitutes for one, and the 'counts only' caveat sets expectations about granularity. The remaining gap is minor: nothing is said about invalid or unresolved municipality slugs or whether the current incomplete month is included.

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%, and the municipality parameter's description already points to find_municipality for resolving the slug, while the work_type enum documents each value. The description adds only that the work-type breakdown is one of the reported dimensions; it contributes no extra syntax or format detail, 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 opens with a specific verb-and-resource pairing ('How many building-permit notices ... one Dutch municipality published recently') and enumerates the exact metrics returned (60/30-day counts, prior 30 days, new applications, grants, work-type breakdown, monthly total and national rank). The 'one Dutch municipality' scoping implicitly separates it from province_permit_counts and work_type_nationwide, but no sibling is named 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?

Usage is implied by the scope statement: a single-municipality lookup rather than a province or nationwide query. However, there is no explicit when-to-use or when-not-to-use guidance, and no routing hint toward work_type_nationwide or province_permit_counts for those broader questions.

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