Nomad Stays

createStayApplication

Start a new Stay Application for the caller. Any fields can be supplied now or filled in later via saveStayApplication — the applicant's name defaults from their Nomad Stays profile if not supplied. Call getCountryOptions and getBusinessModelOptions first to resolve stayCountryId/postalCountryId/businessModelId, since country-specific rules (VAT number, tourism number, permitted business models) are enforced server-side and rejections name the specific field/reason. Requires NOMADSTAYS_MCP_AGENT_TOKEN.

Input Schema

TableJSON Schema

Name	Required	Description
`zip`	No
`city`	No
`state`	No
`mobile`	No
`street`	No
`website`	No
`comments`	No
`stayName`	No
`vatNumber`	No	Required if the postal country's vatNumberRequired flag is true (see getCountryOptions)
`hasKitchen`	No
`businessName`	No
`monthlyPrice`	No	Indicative monthly wholesale price in US dollars (USD) — the application is always priced in USD. Packages are priced in the owner's chosen currency later, after approval.
`downloadSpeed`	No
`numberOfRooms`	No
`stayCountryId`	No	tbCountry.CountryId for where the Stay is actually located — this is the country the application itself is filed under. Use getCountryOptions to find a value.
`tourismNumber`	No	Required if the stay country's tourismNumberRequired flag is true (see getCountryOptions)
`applicantEmail`	No
`workFacilities`	No
`businessModelId`	No	tbBusinessModel.EntryID — use getBusinessModelOptions. If the stay country's bookingModelsRestricted flag is true, only a 'StayDirect'-prefixed model is accepted.
`postalCountryId`	No	tbCountry.CountryId for the applicant's billing/postal address — used only to check whether a VAT number is required, and stored on the member's business profile (not on the application itself). Use getCountryOptions to find a value.
`applicantLastName`	No	Overrides the profile default for this application only — does not change the member's profile
`laundryFacilities`	No
`applicantFirstName`	No	Overrides the profile default for this application only — does not change the member's profile
`availabilitySupplier`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 3, 2026

changedInput schema / properties / businessModelId / description

Previous value: -"tbBusinessModel.EntryID — use getBusinessModels. If the stay country's bookingModelsRestricted flag is true, only a 'StayDirect'-prefixed model is accepted."New value: +"tbBusinessModel.EntryID — use getBusinessModelOptions. If the stay country's bookingModelsRestricted flag is true, only a 'StayDirect'-prefixed model is accepted."

addedInput schema / properties / monthlyPrice / description

Added value: +"Indicative monthly wholesale price in US dollars (USD) — the application is always priced in USD. Packages are priced in the owner's chosen currency later, after approval."

changedInput schema / properties / postalCountryId / description

Previous value: -"tbCountry.CountryId for the applicant's billing/postal address — used only to check whether a VAT number is required, and stored on the member's business profile (not on the application itself). Use getCountries to find a value."New value: +"tbCountry.CountryId for the applicant's billing/postal address — used only to check whether a VAT number is required, and stored on the member's business profile (not on the application itself). Use getCountryOptions to find a value."

changedInput schema / properties / stayCountryId / description

Previous value: -"tbCountry.CountryId for where the Stay is actually located — this is the country the application itself is filed under. Use getCountries to find a value."New value: +"tbCountry.CountryId for where the Stay is actually located — this is the country the application itself is filed under. Use getCountryOptions to find a value."

changedInput schema / properties / tourismNumber / description

Previous value: -"Required if the stay country's tourismNumberRequired flag is true (see getCountries)"New value: +"Required if the stay country's tourismNumberRequired flag is true (see getCountryOptions)"

changedInput schema / properties / vatNumber / description

Previous value: -"Required if the postal country's vatNumberRequired flag is true (see getCountries)"New value: +"Required if the postal country's vatNumberRequired flag is true (see getCountryOptions)"

AddedJul 31, 2026

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 a non-destructive, non-open-world write; the description goes well beyond that by disclosing the required auth token (NOMADSTAYS_MCP_AGENT_TOKEN), that country-specific rules are enforced server-side with rejections naming the field and reason, and that applicant name defaults from the Nomad Stays profile.

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 dense sentences, front-loaded with the core action and the saveStayApplication routing hint before the prerequisite and auth details. Nothing is redundant, though the sentence on country rules is long and could be trimmed.

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 24-parameter, zero-required, no-output-schema tool, the description covers the essentials an agent needs to invoke it correctly: auth, prerequisite lookups, defaulting behavior, and failure semantics. The gap is the undocumented majority of optional fields, which the schema also leaves bare.

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 only 33% across 24 parameters, so the description must compensate, and it does so only partially: it explains the country/business-model resolution path and the firstName/lastName override semantics, but leaves roughly two-thirds of the parameters (address, facilities, pricing, rooms, availabilitySupplier, etc.) with no added meaning in either schema or description.

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?

States a specific verb and resource ('Start a new Stay Application') and immediately scopes it to the caller. It explicitly distinguishes itself from saveStayApplication, which the agent would otherwise confuse with this create/start operation.

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?

Tells the agent when to use this versus the alternative: create now and fill gaps later via saveStayApplication. It also prescribes the prerequisite lookup tools (getCountryOptions, getBusinessModelOptions) and explains why they are needed before calling.

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

All Nomad 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.

createStayApplication

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources