Skip to main content
Glama

lisbon_street_works

Street works and public-space occupations in Lisbon: what is (or will be) blocking a street.

Two official sources: licensed temporary occupations of public space (filming, events, scaffolding, containers...) and the city's road and pavement works in progress or planned. Args: parish: freguesia, e.g. "Arroios", "Santa Maria Maior", "Belém". street: part of a street name (works only), e.g. "Avenida da República". lat, lon: within radius_m metres of a point (max 3000). day: ISO date the occupation must cover; default today.

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

Input Schema

NameRequiredDescriptionDefault
dayNo
latNo
lonNo
limitNo
parishNo
streetNo
radius_mNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose non-obvious behavior: there are two distinct official sources merged into one result, the street filter applies only to works, radius is capped at 3000 m, and day defaults to today and means the occupation must cover that date. Gaps remain around what happens with no filters at all, ordering, and the undocumented limit parameter.

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?

Front-loaded with a one-line purpose, then a short source sentence, then a compact args list. Parenthetical examples are useful rather than filler. Slightly verbose in wording but no sentence is wasted.

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?

An output schema exists, so return values need not be described. However, for a 7-parameter, two-source aggregation tool, the description omits how filters combine, what an unfiltered call returns, and what limit controls — all things an agent needs to call it well.

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 description coverage is 0%, yet the description explains six of the seven parameters with concrete examples ('Arroios', 'Avenida da República'), the 3000 m radius cap, and the day default. The limit parameter is left entirely unexplained, which is the main miss.

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 opening sentence names the resource precisely: street works and public-space occupations in Lisbon, framed as 'what is (or will be) blocking a street'. It also names the two underlying sources (licensed temporary occupations and city road/pavement works), which sharpens what the results actually contain. It does not explicitly contrast with a sibling, so it stops short of a 5.

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: an agent can infer this is the tool for street closures, but the description never says when to prefer it or when not to (e.g. versus lisbon_events for a film shoot that is an event rather than an occupation). The per-filter hints go partway toward guidance but are framed as argument documentation, not when-to-use rules.

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.