Skip to main content
Glama

Consulta PDM (Portugal)

PDM of a municipality

pdm_concelho
Read-onlyIdempotent

Land-use categories of the PDM (municipal master plan) of a Portuguese municipality, with buildable, floor-area index, maximum floors and regulation articles, the plan in force, and links to the municipality page and the map on pdm.xyzbim.eu. Accepts the municipality name (e.g. "Figueira da Foz", accents optional) or its 4-digit DICO code. Field values are in Portuguese. (PT: o PDM de um concelho.)

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": {
      "concelho": "<concelho>"
    },
    "name": "pdm_concelho"
  }
}

Input Schema

NameRequiredDescriptionDefault
concelhoYesmunicipality name or 4-digit DICO code

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely useful context beyond that: field values are in Portuguese, accents in the municipality name are optional, and the response includes external links to the municipality page and pdm.xyzbim.eu. It stops short of describing error behavior for invalid inputs.

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 return payload is front-loaded in the first clause and input formats follow, with only a small parenthetical Portuguese gloss at the end. Slightly list-heavy but no sentence is wasted.

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 carries the burden of describing return values and does so by enumerating the field groups plus the plan-in-force and links. What is missing is disambiguation guidance for ambiguous names and any indication of response size or language of keys versus values.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it gives a concrete example ('Figueira da Foz'), states that accents are optional, and specifies the code is 4 digits. That is more than the schema's terse 'municipality name or 4-digit DICO code'.

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 (PDM land-use categories for a Portuguese municipality) and enumerates the returned fields (buildable, floor-area index, max floors, regulation articles, plan in force, links). It is clear what the tool does, but it never mentions the sibling pdm_terreno, so an agent gets no explicit differentiation between the two.

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 only implied: it is a lookup keyed on municipality name or DICO code. There is no statement of when to prefer this over pdm_terreno, no prerequisites, and no note on what happens with an unknown or ambiguous municipality name (e.g. multiple matches).

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