Skip to main content
Glama

Nomad Stays

by io.github.nomadstays
OverviewDiscussionsAdmin

createStayPackage

Create a new pricing package on a Stay, optionally with initial price tiers. Requires an MCP agent token scoped to the owning account.

Input Schema

NameRequiredDescriptionDefault
listedNoOPTIONAL: whether the package is publicly listed
maxPaxNoOPTIONAL: max occupancy for this package
pricesNoOPTIONAL: initial price tiers. If supplied, replaces all price rows for the package. Exactly one entry per 7/14/21/30-night tier used.
stayIdYesThe Stay's EntryID
endDateNoOPTIONAL: last check-in date this package is available for
startDateNoOPTIONAL: first check-in date this package is available for
currencyFKYesREQUIRED: the currency this package is priced in — an id from getCurrencyOptions. Packages can use any supported currency; ASK the owner which one, never assume USD. All buyPrice values are in this currency.
roomTypeFKNoOPTIONAL: room type id this package covers. Call getRoomTypeOptions for valid values.
stayRoomFKNoSTRONGLY RECOMMENDED: the specific room this package covers (tbStaysRoom.EntryID). Call getMyStayRooms to find the right room id first. If omitted, the server guesses a room matching roomTypeFK, which may pick the wrong one when a Stay has multiple rooms of the same type.
descriptionNoOPTIONAL: package description
packageNameYesPackage name
advertisingEndpointNoOPTIONAL: only usable on Advertising-business-model Stays — ignored otherwise, matching the host UI which hides this field for all other business models. Check getBusinessModelOptions / the Stay's businessModelFK before setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / currencyFK / description
      Previous value: -"OPTIONAL: currency id. Call getCurrencyOptions for valid values."New value: +"REQUIRED: the currency this package is priced in — an id from getCurrencyOptions. Packages can use any supported currency; ASK the owner which one, never assume USD. All buyPrice values are in this currency."
    • changedInput schema / required
      Previous value: -[
-  "stayId",
-  "packageName"
-]New value: +[
+  "stayId",
+  "packageName",
+  "currencyFK"
+]
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the safe-create profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description's job is to add context. It contributes the auth requirement (agent token scoped to the owning account), which is genuinely beyond the annotations. It says nothing about idempotency, duplicate-name behavior, or what the call returns, so it adds one useful fact but not rich behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, and the core action is front-loaded ahead of the conditional detail. Nothing is repeated from the title or schema.

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 12-parameter mutation relying on a 100%-covered schema plus annotations, the description covers purpose and auth adequately. The one real gap is that no output schema exists and the description never says what comes back (e.g. the new package id), which an agent chaining into updateStayPackage would want.

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 100%, and the schema is unusually rich — it already explains the tier enum, the buyPrice/sellPrice derivation, and the currency/room prerequisites. The description's 'optionally with initial price tiers' merely restates the prices parameter. Baseline 3 is correct here since the schema does all the heavy lifting.

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?

States a specific verb and resource: 'Create a new pricing package on a Stay', with a secondary clause covering the optional tiers. The verb 'Create' separates it cleanly from the sibling updateStayPackage and deleteStayPackage without needing to name them. Slightly short of a 5 because it never acknowledges those siblings or the getMyStayPackages read path.

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?

Gives one prerequisite ('Requires an MCP agent token scoped to the owning account') and notes the tiers are optional, which is useful context for invocation. However it offers no when-to-use/when-not guidance and never points at updateStayPackage for modifying an existing package. Usage is implied by the verb rather than stated.

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