Skip to main content
Glama
Sign In

Nomad Stays

by io.github.nomadstays
OverviewDiscussionsAdmin

confirmStayBooking

Idempotent

As a connected supplier, confirm a booking on one of your Stays that your system accepted as pending (confirmed: true with your supplierReference), or refuse it (confirmed: false with a reason). Confirm within 30 minutes of the booking or the Nomad Stays team is alerted. A refusal is a refused booking under the Stay Partner terms: the room is taken off sale automatically and the client must be relocated to an equal or better room. Requires an MCP agent token scoped to the owning account.

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": {
      "pnr": "<pnr>",
      "confirmed": "<confirmed>"
    },
    "name": "confirmStayBooking"
  }
}

Input Schema

NameRequiredDescriptionDefault
pnrYesThe Nomad Stays booking reference (booking_reference in create_booking)
reasonNoWhy the booking is refused (required when refusing)
confirmedYestrue to confirm, false to refuse
supplierReferenceNoYour booking reference (required when confirming)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare it is not read-only, is idempotent, and non-destructive; the description adds substantially more: the 30-minute SLA before the Nomad Stays team is alerted, the concrete effect of a refusal (room removed from sale, client relocation obligation), and the MCP agent token scoping requirement. This is exactly the behavioral context annotations cannot carry.

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?

Three sentences, each doing distinct work: operation, deadline, and refusal consequence, with the action choice front-loaded. Slightly dense compound clauses ('confirmed: true with your supplierReference') but no wasted sentences.

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 four-parameter mutation tool with no output schema, the definition covers the operation, the branching requirements, the timing obligation, and the downstream effects of refusal. Only the return value / success signal is left implicit, which is a minor gap.

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% and the schema already documents pnr, confirmed, reason, and supplierReference including the conditional 'required when confirming/refusing' notes. The description restates those conditional pairings but adds no format or validation detail beyond them, so baseline 3 applies.

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?

The description names a specific verb pair (confirm / refuse) and a specific resource (a booking on one of your Stays accepted as pending), which cleanly separates it from bookStay, cancelBooking, and listMyStayBookings. An agent can identify the operation without opening the schema.

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

Usage Guidelines5/5

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

It states the triggering condition (a booking your system accepted as pending), both available actions, the 30-minute deadline that gates confirmation, and what a refusal commits you to. That is explicit when-to-use plus the consequence-based trade-off between the two branches.

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

All Nomad Stays toolsInspect
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