Skip to main content
Glama
Sign In

Nomad Stays

by io.github.nomadstays
OverviewDiscussionsAdmin

listMyStayBookings

Read-only

List the bookings on one of your Stays (from 30 days ago by default), with dates, rooms, guests, your price and the supplier status (pending_push, pending, confirmed, refused, cancelled…) and your supplier reference, so your system can reconcile with Nomad Stays. Never shows the booking fee the client paid Nomad Stays. 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": {
      "stayId": "<stayId>"
    },
    "name": "listMyStayBookings"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoOnly bookings checking out on or after this date (yyyy-MM-dd). Default: 30 days ago
stayIdYesThe Stay's EntryID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/non-destructive annotations, the description adds meaningful behavior: the default 30-day lookback, the returned fields and supplier statuses, the supplier reference, the explicit omission of the client booking fee, and the required account-scoped MCP agent token. It does not discuss pagination, sorting, or result limits, so it stops short of fully transparent.

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 description is front-loaded with the core action and scope, and the follow-up sentences cover the hidden fee and auth precondition without unnecessary filler. The first sentence is dense and packs several return fields into one long clause, but it remains purposeful.

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 two-parameter read-only listing tool with no output schema, the description does the important work of naming returned fields, statuses, the hidden-fee boundary, and the token requirement. It is nearly complete, though it leaves pagination and ordering behavior unaddressed.

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 both parameters are already documented. The description restates the 30-day default for 'from' and identifies that the stay is 'one of your Stays,' but it adds no new syntax, constraints, or meaning beyond the input schema.

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 description clearly states a specific verb and resource: list bookings on one of your Stays, scoped by stay and a default 30-day lookback. It implicitly distinguishes this per-Stay listing from the broader sibling listMyBookings by saying 'on one of your Stays,' though it never names that alternative explicitly.

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

Usage Guidelines3/5

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

The reconciliation use case is stated, and the default date range is useful context. However, there is no explicit guidance on when to choose this tool over listMyBookings or getBookingStatus, nor any when-not conditions.

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