Skip to main content
Glama

Look up a property by name

lookup_by_name
Read-onlyIdempotent

Find passports by property name: exact or prefix match, at least 3 characters, at most 10 results, exact match first, then alphabetical. Optionally limited to a municipality. 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

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of labels in the result; defaults to en
nameYesProperty name or its beginning, at least 3 characters
municipalityNoExact municipality name

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / results / items / properties / verification / properties / tier / description
      Previous value: -"Verification tier (docs: ADR 0012, 0017, 0024, 0025). L0 unclaimed: facts read from the operator's official website, nothing proven, the operator has not claimed the page; contact only through send_inquiry. L2 listing verified: the operator proved control of the platform listing (calendar export link with the listing id, platform email with a valid DKIM signature, or channel manager); since 2026-11-07 also their right to manage the property (LA or L3), and earlier L2 stands as it was reached. L2c listing calendar proven (Booking, Vrbo): the operator blocked a random date Ospitario named in that platform's calendar export within 48 hours; no new L2c since 2026-11-07. LA right to manage verified (document review): Ospitario's admin checked documents tying the operator to this property (registration record, deed, lease, mandate or company register); a person found them consistent, without eID, so it does not prove who holds the account and never proves a platform listing. L3 operator verified: the operator's eID identity (SPID/CIE) matches the CIN holder in the national register's PDF. L4 document verified (automated check): an ownership, lease or mandate document is consistent with that identity and the property; it states consistency, not authenticity. L5 manually verified: a reviewer checked the document (an optional upgrade; it does not affect search order)."New value: +"Verification tier (docs: ADR 0012, 0017, 0024, 0025). L0 unclaimed: facts read from the operator's official website, nothing proven, the operator has not claimed the page; contact only through send_inquiry. L2 listing verified: the operator proved control of the platform listing (calendar export link with the listing id, platform email with a valid DKIM signature, or channel manager); since 2026-11-07 also their right to manage the property (LA or L3), and earlier L2 stands as it was reached. L2c listing calendar proven (Booking, Vrbo): the operator blocked a random date Ospitario named in that platform's calendar export within 48 hours; no new L2c since 2026-11-07. LA right-to-manage documents reviewed: Ospitario's admin checked documents tying the operator to this property (registration record, deed, lease, mandate or company register); a person found them consistent, without eID, so it does not prove who holds the account and never proves a platform listing. L3 operator verified: the operator's eID identity (SPID/CIE) matches the CIN holder in the national register's PDF. L4 document verified (automated check): an ownership, lease or mandate document is consistent with that identity and the property; it states consistency, not authenticity. L5 manually verified: a reviewer checked the document (an optional upgrade; it does not affect search order)."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, closed-world, non-destructive); the description adds substantial behavior beyond them: a 10-result cap, exact-match-first then alphabetical ordering, per-result provenance tiers (L2/L2c, L3, LA, L0), registration-number verification status, and the commission-free direct-contact model.

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 matching rules and limits are front-loaded and every clause carries information, but the middle sentence is a long run-on that packs tier codes, verification status and commercial terms together, which makes it denser than needed.

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 usefully explains what a result represents and what an empty result means; the main gap is that tier codes (L2/L2c, L3, LA) are introduced without full definition and behavior when more than 10 properties match is only implied.

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 coverage is 100%, so name, municipality and lang are already documented, including the 3-character minimum; the description only echoes that minimum and adds result-count/ordering behavior rather than new parameter meaning. Baseline 3 applies when the schema carries the parameter load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Find passports by property name') plus the matching mode (exact or prefix), which distinguishes it from lookup_by_url and get_passport without needing to open their schemas.

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?

Gives concrete selection rules (exact or prefix match, minimum 3 characters, optional municipality filter) and clarifies the empty-result case, but never names an alternative tool or states when another lookup path should be preferred.

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