Skip to main content
Glama

Consulta PDM (Portugal)

PDM rules at a point

pdm_terreno
Read-onlyIdempotent

What the Portuguese municipal master plan (PDM, Plano Diretor Municipal) allows at a point (WGS84 latitude, longitude) or on a plot polygon: municipality, land-use category from the official land-use map, whether it is buildable, floor-area index, maximum floors, regulation articles, RAN and REN reserves, national easements and restrictions it touches (Natura 2000 SAC, protected areas, road, rail, power line, aviation and military easements, reservoirs, groundwater abstraction protection), applicable provisional planning norms, municipal notices requiring confirmation, their official sources, and a link to the full analysis on pdm.xyzbim.eu. Mainland Portugal and the Azores. Field values are in Portuguese. Each result carries its source attribution. With a plan key in the connector URL (?chave=), the full regulation fields (height, coverage, minimum plot area, uses, conditions) are returned and the plan quota is used. (PT: o que o PDM permite num ponto ou num terreno.)

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

Input Schema

NameRequiredDescriptionDefault
latNoWGS84 latitude (e.g. 40.15); with lon, a 20 m x 20 m plot centred on the point
lonNoWGS84 longitude (e.g. -8.86)
poligonoNooptional plot polygon instead of lat/lon: 3 to 500 [longitude, latitude] vertices (WGS84)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / lat / description
      Previous value: -"WGS84 latitude (e.g. 40.15)"New value: +"WGS84 latitude (e.g. 40.15); with lon, a 20 m x 20 m plot centred on the point"
    • addedInput schema / properties / poligono
      Added value: +{
      +  "description": "optional plot polygon instead of lat/lon: 3 to 500 [longitude, latitude] vertices (WGS84)",
      +  "items": {
      +    "items": {
      +      "type": "number"
      +    },
      +    "maxItems": 2,
      +    "minItems": 2,
      +    "type": "array"
      +  },
      +  "maxItems": 500,
      +  "minItems": 3,
      +  "type": "array"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "lat",
      -  "lon"
      -]
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already establish readOnly/idempotent/non-destructive, and the description still adds substantial behavior beyond them: field values are in Portuguese, every result carries source attribution, a plan key (?chave=) changes the returned fields and consumes plan quota, municipal notices may require confirmation, and coverage is limited to mainland Portugal and the Azores. Those are real operational caveats (data reliability, conditional output shape, geographic limit) an agent cannot get from 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 lead clause front-loads purpose before the long enumeration of returned data, which is the right order. The middle clause is a dense run-on list of reserve and easement types that hurts scannability, and the trailing Portuguese gloss adds little, but no sentence is purely filler.

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 correctly carries the burden of describing return values, and it does so thoroughly, including language, attribution, and the plan-key variant. The remaining gap is input behavior: with zero required parameters it never says what the tool does when neither lat/lon nor poligono is provided.

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%, so the schema already explains lat/lon, the 20 m x 20 m plot default, and the polygon vertex format and limits. The description only restates the point-vs-polygon duality and adds nothing on formats, precedence when both are supplied, or coordinate validation, so the baseline 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 names a specific resource and scope: what the Portuguese PDM allows at a WGS84 point or on a plot polygon, and enumerates the concrete outputs (land-use category, buildability, floor-area index, RAN/REN reserves, easements). It is unambiguous what the tool answers, but it never names the sibling pdm_concelho or states the boundary between point-level and municipality-level queries, leaving that differentiation to inference.

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: the reader gathers that it is for a point or a plot polygon in mainland Portugal/Azores, and the closing sentence reveals that a plan key in the connector URL switches to full regulation fields. There is no explicit when-to-use vs. when-not guidance, no statement of what happens if no coordinates or polygon are supplied, and no routing to the sibling tool.

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