Skip to main content
Glama

OpenStays Property Passports

Get one OpenStays Property Passport

get_property_passport
Read-onlyIdempotent

Retrieve one exact public Property Passport returned by search_stays. Accepts only a canonical https://openstays.ai/stays/... URL. The Passport follows the schema at https://openstays.ai/passport-schema/latest/passport.schema.json.

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

Input Schema

NameRequiredDescriptionDefault
profileUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds real value beyond them by pinning the accepted input to canonical openstays.ai URLs and by pointing at the external JSON schema that defines the returned Passport. Auth requirements and rate limits remain unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with zero filler: purpose first, input constraint second, return-shape reference third. Every sentence carries information not already in the schema or annotations.

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?

For a single-parameter read tool with no output schema, the description covers purpose, the sole input, and where the response shape is documented. The main residual gap is that the external schema URL may not be retrievable by the agent, and no failure behavior for invalid or stale URLs is described.

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%, but the schema itself carries a format and an explicit URL regex, and the description reinforces the same constraint in prose. It adds meaning the regex cannot express: the URL must be one that came from a prior search_stays result, not merely a string that matches the pattern.

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?

States a specific verb ("Retrieve") and a specific resource ("one exact public Property Passport"), and ties it to the sibling by noting the Passport is "returned by search_stays". An agent can distinguish this single-item fetch from the search tool, though the contrast is implied rather than spelled out.

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?

The origin constraint ("returned by search_stays") tells the agent this is a follow-up call on results from the sibling, which is clear usage context. It gives no explicit when-not guidance or statement about error behavior for non-matching URLs beyond "Accepts only a canonical ... URL".

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