Skip to main content
Glama

Nomad Stays

by io.github.nomadstays
OverviewDiscussionsAdmin

createExperienceApplication

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNo
cityNo
stateNo
maxPaxNoMaximum participants
mobileNo
streetNo
daysQtyNoMinimum 4 days, enforced server-side
websiteNo
commentsNo
vatNumberNoRequired if the postal country's vatNumberRequired flag is true (see getCountryOptions)
hasKitchenNo
descriptionNo
businessNameNo
hasInsuranceNo
monthlyPriceNoPrice per person (USD)
downloadSpeedNo
tourismNumberNoRequired if the experience country's tourismNumberRequired flag is true (see getCountryOptions)
applicantEmailNo
experienceNameNo
workFacilitiesNo
businessModelIdNotbBusinessModel.EntryID — use getBusinessModelOptions. If the experience country's bookingModelsRestricted flag is true, only a 'StayDirect'-prefixed model is accepted.
postalCountryIdNotbCountry.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.
applicantLastNameNoOverrides the profile default for this application only — does not change the member's profile
laundryFacilitiesNo
applicantFirstNameNoOverrides the profile default for this application only — does not change the member's profile
experienceCountryIdNotbCountry.CountryId for where the experience actually takes place — this is the country the application itself is filed under. Use getCountryOptions to find a value.
availabilitySupplierNo
overnightLocationsQtyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / businessModelId / description
      Previous value: -"tbBusinessModel.EntryID — use getBusinessModels. If the experience country's bookingModelsRestricted flag is true, only a 'StayDirect'-prefixed model is accepted."New value: +"tbBusinessModel.EntryID — use getBusinessModelOptions. If the experience country's bookingModelsRestricted flag is true, only a 'StayDirect'-prefixed model is accepted."
    • changedInput schema / properties / experienceCountryId / description
      Previous value: -"tbCountry.CountryId for where the experience actually takes place — this is the country the application itself is filed under. Use getCountries to find a value."New value: +"tbCountry.CountryId for where the experience actually takes place — this is the country the application itself is filed under. Use getCountryOptions to find a value."
    • 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 / tourismNumber / description
      Previous value: -"Required if the experience country's tourismNumberRequired flag is true (see getCountries)"New value: +"Required if the experience 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)"
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false); the description adds substantial context beyond that: auth token requirement, server-side enforcement of country rules, that rejections name the specific field/reason, the 4-day minimum, and the profile-default behavior for the applicant name. This is rich behavioral disclosure not present in structured fields.

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?

Front-loaded with the core action, then prerequisites, then constraints. Every clause carries information (routing, min-days, auth), though the single dense paragraph packs several distinct rules together, slightly reducing scannability.

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 28-parameter mutation tool with no output schema, the description covers the workflow (create now, fill later), prerequisite lookups, validation behavior, and auth. It is nearly complete for correct invocation, with only the large set of undocumented optional fields leaving residual gaps.

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 description coverage is only 36% across 28 parameters, so the description must compensate. It does add meaning for the key foreign keys (experienceCountryId vs postalCountryId and their differing storage/use), the minimum-days rule for daysQty, and applicant name defaulting, but the bulk of parameters (maxPax, monthlyPrice, availabilitySupplier, workFacilities, etc.) remain undocumented in both places.

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 Experience Application for the caller') and distinguishes itself from the sibling saveExperienceApplication by framing this as the creation step. An agent can tell it apart from createStayApplication/createCoworkingApplication by the 'Experience' resource noun.

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?

Explicitly names the alternative path (saveExperienceApplication for filling fields in later) and prescribes prerequisites: 'Call getCountryOptions and getBusinessModelOptions first to resolve experienceCountryId/postalCountryId/businessModelId.' The when-to-use and pre-call ordering are both spelled out rather than inferred.

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