Skip to main content
Glama

Nomad Stays

by io.github.nomadstays
OverviewDiscussionsAdmin

getStaysByBudget

Read-only

Search for stays that fit within a budget for a given duration. Country is OPTIONAL - can search globally or filter by specific country. Perfect for queries like 'Find me somewhere to stay for 1 month under EUR 1000' or 'Find me a place in Spain for 1 month under EUR 1000'.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default: 15)
currencyYesCurrency code (e.g., 'EUR', 'USD', 'GBP')
maxPriceYesMaximum price for the entire duration (e.g., 1000 for EUR 1000)
continentNoOPTIONAL: Continent name (e.g., 'Europe', 'Asia', 'Africa'). Filters results to stays in countries on this continent. If omitted, searches all continents globally.
checkInDateNoOPTIONAL: Check-in date. Can be a full date (e.g., '2026-05-15'), a month name (e.g., 'May' ? uses May 1st), or omit for today (2026-01-19)
countryCodeNoOPTIONAL: 2-letter country code (e.g., 'ES', 'PT') or country name (e.g., 'Spain'). If omitted, searches all countries globally.
durationDaysYesDuration of stay in days (e.g., 30 for 1 month, 90 for 3 months)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / continent
      Added value: +{
+  "description": "OPTIONAL: Continent name (e.g., 'Europe', 'Asia', 'Africa'). Filters results to stays in countries on this continent. If omitted, searches all continents globally.",
+  "type": "string"
+}
  2. Changed6 schema fields changed
    • changedInput schema / properties / checkInDate / description
      Previous value: -"OPTIONAL: Check-in date. Can be a full date (e.g., '2026-05-15'), a month name (e.g., 'May' ? uses May 1st), or omit for today"New value: +"OPTIONAL: Check-in date. Can be a full date (e.g., '2026-05-15'), a month name (e.g., 'May' ? uses May 1st), or omit for today (2026-01-19)"
    • changedInput schema / properties / countryCode / description
      Previous value: -"2-letter country code or country name (OPTIONAL - omit to search all countries)"New value: +"OPTIONAL: 2-letter country code (e.g., 'ES', 'PT') or country name (e.g., 'Spain'). If omitted, searches all countries globally."
    • changedInput schema / properties / currency / description
      Previous value: -"Currency code (e.g., 'EUR', 'USD')"New value: +"Currency code (e.g., 'EUR', 'USD', 'GBP')"
    • changedInput schema / properties / durationDays / description
      Previous value: -"Duration of stay in days (e.g., 30 for 1 month)"New value: +"Duration of stay in days (e.g., 30 for 1 month, 90 for 3 months)"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results (default: 15)"New value: +"Maximum number of results to return (default: 15)"
    • changedInput schema / properties / maxPrice / description
      Previous value: -"Maximum price for the entire duration"New value: +"Maximum price for the entire duration (e.g., 1000 for EUR 1000)"
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds only the country-optional/global-search note, which is largely duplicated in the schema, and says nothing about result ordering, pagination, or the limit behavior.

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?

Three sentences, front-loaded with the core purpose and examples. The middle sentence about the optional country overlaps with the schema but is short and does not bloat the definition.

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 read-only search tool with a fully documented schema and safety annotations, the definition covers purpose and example usage adequately. It omits any hint about return shape or ordering (no output schema exists), which leaves a modest gap.

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%, so all seven parameters are already documented in the schema. The description restates the optional-country behavior but adds no format, syntax, or constraint details beyond what the schema provides, so the baseline of 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 (Search) and resource (stays) constrained by budget and duration, which is a distinct filter axis from siblings like getStaysByAmenities or getStaysByCountry. It does not explicitly name or contrast any sibling, but the budget/duration scope makes it readily distinguishable.

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?

Two concrete example queries ('somewhere to stay for 1 month under EUR 1000' and 'a place in Spain for 1 month under EUR 1000') give clear context for when to reach for this tool. It stops short of naming alternatives or stating when NOT to use it.

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