Spann Stays

get_spann_journey_status

Read-only

Resume a Spann handoff by its opaque journey credential. Preparation reports are assistant-reported; booking and payment remain unconfirmed until independently reconciled with the provider. Confirmed states require an independently authorized property/provider receipt. Never send guest/card details.

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": {
      "journey_id": "<journey_id>",
      "resume_token": "<resume_token>"
    },
    "name": "get_spann_journey_status"
  }
}

Input Schema

Name	Required	Description	Default
`journey_id`	Yes
`resume_token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3/5.0

Behavior4/5

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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), and the description adds meaningful semantics: preparation reports are assistant-reported, booking/payment are unconfirmed until reconciled with the provider, and confirmed states require an authorized receipt. That is genuine trust-model context beyond the annotations, though the verb "resume" sits in mild tension with a read-only hint and is left unexplained.

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?

Four short sentences with no filler, and the core action plus the safety constraint are front-loaded. The opening sentence is slightly muddled about whether the operation is a resume or a status read, which costs a bit of clarity.

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 two-parameter read tool with no output schema, the description does well on the meaning of returned states but says nothing about what the response actually contains (status values, journey progress) or how the two parameters combine. It is adequate but leaves real gaps for an agent invoking it cold.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 carry the parameter burden, and it only vaguely refers to an "opaque journey credential." It does not clarify that journey_id and resume_token are two distinct required values, nor what format or provenance each has.

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

Purpose3/5

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

The description says it will "Resume a Spann handoff by its opaque journey credential," which identifies a resource and action but conflicts with the tool name's framing of retrieving status. An agent cannot easily tell whether this resumes a workflow, fetches a status, or both, and it is not distinguished from the sibling get_spann_booking_confirmation.

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?

There is no guidance on when to call this tool versus siblings like get_spann_booking_confirmation or prepare_discovered_stay, nor any stated prerequisites beyond possessing the credential. The cautions describe how to interpret results, not when to select this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Spann Stays tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?