Skip to main content
Glama

Permit counts for one province

province_permit_counts
Read-onlyIdempotent

Building-permit notices in one Dutch province in the last 60 and 30 days, by work type, with the municipalities that published the most. Counts only.

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": {
      "province": "<province>"
    },
    "name": "province_permit_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
provinceYesProvince URL slug, e.g. gelderland or noord-holland.
work_typeNoWork type, e.g. dakkapel (dormer), aanbouw (extension), kozijnen (window frames).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 substantive behavior beyond that: two fixed time windows (60 and 30 days), a work-type breakdown, inclusion of the top-publishing municipalities, and the 'counts only' restriction meaning no individual notices are returned. It does not say how many municipalities are listed or in what order.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with no filler: scope, time windows, dimension, secondary output and output restriction are all front-loaded, and the closing 'Counts only' earns its place by preventing an agent from expecting permit records.

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 description must convey the return shape and it largely does: counts split across 60- and 30-day windows, broken out by work type, plus leading municipalities. It stops short of specifying the number of municipalities returned or ordering, which is a small remaining gap for a two-parameter read tool.

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 both parameters are enum-constrained with examples, so the schema carries the semantics. The description adds only the framing that province scopes to a single province and work_type drives the breakdown; it gives no extra syntax or default behavior. Baseline 3 is appropriate.

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 resource (building-permit notices), a specific scope (one Dutch province, last 60 and 30 days), a breakdown (work type) and an output nature (counts only). An agent knows exactly what it returns. It does not name its siblings (municipality_permit_counts, work_type_nationwide), so the province-vs-municipality-vs-nationwide distinction must be inferred.

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?

There is no explicit when-to-use or when-not-to-use statement and no alternative is named. The phrase 'in one Dutch province' plus 'Counts only' implicitly signals that this is the aggregate provincial view rather than a per-notice or per-municipality query, but routing between this and municipality_permit_counts is left to inference.

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