Skip to main content
Glama

tourism_places

Official tourism places in Portugal, near a point or in a municipality/region.

Args: kind: one of blue_flag_beaches, surf_spots, golf, spas, unesco, historic_villages, schist_villages, wine_villages, mountain_villages, marinas, walking_routes, santiago_ways, hotels. place: municipality, parish, district or region name, e.g. "Cascais", "Algarve", "Peniche". name: part of the name, e.g. "Nazaré", "Pestana". lat, lon: closest first, within radius_km (max 200).

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": {
      "kind": "<kind>"
    },
    "name": "tourism_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
kindYes
nameNo
limitNo
placeNo
radius_kmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden but does add useful details: results are official tourism places, ordered closest first for geographic queries, and radius is capped at 200 km. It does not mention read-only behavior, permissions, rate limits, or how the limit parameter affects results.

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 description is front-loaded with the core purpose and then uses a compact Args block for parameter guidance. It is not padded with unnecessary prose, though the formatting is utilitarian and leaves a small gap around limit.

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?

For a seven-parameter tool with no annotations and 0% schema description coverage, the description covers most parameter semantics and some behavior. However, it omits the limit parameter and does not explain whether lat/lon must be supplied together or how place/name interact with geographic filtering.

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%, so the description must explain parameters, and it meaningfully documents kind with a long list of allowed values, place and name with concrete examples, lat/lon ordering semantics, and the 200 km radius cap. The main gap is that limit is never mentioned.

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 clearly states the resource and scope: official tourism places in Portugal, retrievable by point proximity or by municipality/region. It does not explicitly say this is a list/search tool or name a sibling alternative, but the resource boundary is easy to understand.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description defines two retrieval modes, near a point or within a municipality/region, but gives no explicit when-to-use guidance and no alternatives or exclusions. An agent must infer its role from the tool name and scope alone.

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.