Skip to main content
Glama

Where Ospitario has homes

list_places
Read-onlyIdempotent

Where Ospitario has public passports: every municipality with at least one, its region (Italy) and country, how many passports (and how many of them unclaimed, tier L0), and its list page. Call it when the traveler names an area, before searching: a place not listed has no passport on Ospitario yet; say so instead of searching it. Coverage is still small and grows week by week. Every result is a property with a proven listing (L2/L2c), a verified operator (L3), a right to manage verified by document review (LA) or, marked L0 and unclaimed, facts from the operator's official website with nothing proven; the result names the tier and the date it was reached, and whether the registration number (Italy: CIN) was checked against the public register. Contact is direct with the operator and commission-free, so the traveler pays no platform fee. No result means nothing proven matches; nothing is inferred, estimated or filled in.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of labels in the result; defaults to en
countryNoISO 3166-1 alpha-2 country code to list: IT, DE, ES, FR or PT; all when omitted

Output Schema

NameRequiredDescriptionDefault
totalYesPublic passports in the places listed
placesYesEvery municipality with at least one public passport, by country, region and name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds substantial behavior: coverage is small and growing weekly, every result carries a provenance tier (L2/L2c, L3, LA, L0), the tier date and whether the CIN was checked against the public register. It also states that nothing is inferred or estimated and that contact is direct and commission-free, which are real expectations an agent needs. This is context well beyond the structured fields.

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 purpose is front-loaded and every clause is substantive rather than filler. However, the single semicolon-chained paragraph packs tier codes (L0, L2/L2c, L3, LA) and provenance detail into the tool-selection text, making it harder to scan than it needs to be for a two-parameter list call.

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?

An output schema exists, yet the description still explains result meaning (tiers, dates, register checks) and, crucially, what an empty result means, which is the key ambiguity for a coverage tool. It is complete for the decision at hand; only the optional country filter is left unexplained, and the schema covers that.

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 carry enums with defaults documented, so the schema does the heavy lifting. The description never mentions the lang or country filter parameters, adding no meaning beyond the schema. Baseline 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 opening clause states a specific resource and scope: every municipality where Ospitario has a public passport, with region, country, counts and list page. It is clearly a coverage-listing tool, distinguishable from lookup_by_name or search_properties. It loses a point only because the purpose statement is buried in a dense, jargon-laden sentence rather than stated in one clean line.

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

Usage Guidelines4/5

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

It gives an explicit trigger ("Call it when the traveler names an area, before searching") and an explicit when-not/next-step ("a place not listed has no passport on Ospitario yet; say so instead of searching it"). No sibling tool is named outright, so the agent must infer that "searching" means search_properties, but the sequencing rule is unambiguous.

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