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

TableJSON 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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful auth context (agent token scoped to owning account), but says nothing else about side effects, permissions beyond token scope, or behavior of the 'replaces all price rows' operation.

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 tight sentences with no filler; the creation action is front-loaded and the auth constraint follows as a distinct prerequisite.

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

Completeness3/5

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

For a 12-parameter creation tool the description is thin, but the schema carries full parameter detail and annotations carry the safety profile and no output schema exists. It covers purpose and one prerequisite but omits any note on tier-replacement semantics or the create-vs-update decision.

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 already explains every parameter in detail (buyPrice/sellPrice computation, currency selection, sale-vs-rental semantics). The description adds only 'optionally with initial price tiers', which the schema already conveys, so baseline 3 applies.

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') and the optional scope ('initial price tiers'). The word 'new' implicitly distinguishes it from updateStayPackage/deleteStayPackage, but the description never names those siblings 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?

Provides a prerequisite ('Requires an MCP agent token scoped to the owning account') and hints that tiers are optional at creation. However, it gives no explicit guidance on when to create a package versus when to update an existing one with updateStayPackage.

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