Skip to main content
Glama
Sign In

Nomad Stays

by io.github.nomadstays
OverviewDiscussionsAdmin

getStaySupplierConnection

Read-only

For Stay Partners whose own system holds availability and bookings (a connected supplier): show a Stay's connection to the partner's MCP server — the server URL, whether an API key is set (never the key itself), whether the Stay is priced by the day, the last sync time and error, and each room's mcpRoomId. Nomad Stays calls the partner's get_allocation, check_availability, create_booking and cancel_booking tools. 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": "getStaySupplierConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
stayIdYesThe Stay's EntryID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses exactly what is returned: server URL, whether an API key is set but never the key itself, daily pricing status, last sync time and error, and each room's mcpRoomId. It also explains the external partner tool calls and the MCP agent token scope requirement, which is valuable operational context.

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 dense but appropriately sized for a tool with several returned fields and auth requirements. It front-loads the connected-supplier condition, though the first sentence is lengthy and could be split for faster scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining return values, and it does so comprehensively: connection URL, masked key status, sync state, errors, and room mappings. It also supplies the authentication requirement needed to invoke the tool successfully.

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?

The schema has 100% description coverage and documents stayId as the Stay's EntryID. The description does not add further meaning or formatting guidance for that parameter, so the baseline of 3 is appropriate.

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 uses a specific verb and resource: 'show a Stay's connection to the partner's MCP server.' It clearly identifies the connected-supplier scenario and distinguishes this read-only inspection tool from the sibling updateStaySupplierConnection.

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?

It states the relevant context clearly: 'For Stay Partners whose own system holds availability and bookings (a connected supplier).' This tells an agent when the tool applies, but it does not explicitly direct the agent to updateStaySupplierConnection when changes are needed or state exclusions.

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