Skip to main content
Glama

Nomad Stays

by io.github.nomadstays

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

TableJSON 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. Dates show when Glama detected each change.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the useful note that country is optional and search can be global or filtered, but this is more parameter semantics than behavioral disclosure. No contradictions or additional behavioral traits are revealed.

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 tightly scoped sentences with example queries that directly map to the schema parameters. No filler or repetition of structured fields; every line earns its place.

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?

The description gives enough context for an agent to understand the primary use case and the optional country behavior. It does not mention limit, checkInDate, or continent, but those are fully documented in the schema, and no output schema exists to explain. Given annotations cover safety, this is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema documents all parameters. The description adds value by pairing parameters in realistic combinations (durationDays=30, maxPrice=1000, currency='EUR') and clarifying that maxPrice applies to the entire duration, which reinforces the schema's wording with concrete examples.

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?

The description states a specific action ('Search for stays') and a clear filtering criterion (budget and duration), with example queries that make the resource and scope easy to grasp. It does not explicitly differentiate itself from sibling tools like getStaysByCountry or getStaysByContinent, though the budget focus makes it reasonably distinct.

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?

The description provides concrete example user queries ('Find me somewhere to stay for 1 month under EUR 1000') that imply when the tool should be used. However, it gives no explicit guidance on when not to use this tool versus alternatives, nor does it mention other getStays* siblings that might also apply.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions differentiating the many getStaysBy* search variants and the four availability tools. However, the overlap between checkStayAvailability, getRoomAvailability, findNearestAvailability, and getAvailabilityByMonth could still cause confusion for an agent, though the descriptions largely mitigate this.

Naming Consistency3/5

The tools mostly follow a verb-noun pattern with get*, update*, create*, and delete* dominating, but the mix of additional verbs (check, find, list, search, signup, book, quote, purchase, submit, save, reorder, upload) and inconsistent noun forms (Stay vs. Stays, MyStay vs. Stay) prevents a fully predictable naming scheme. CamelCase is consistent, but the verb variety is high.

Tool Count1/5

With 76 tools, this server far exceeds the well-scoped range and even the 50+ threshold for extreme mismatch. While the platform covers multiple domains, this many tools is overwhelming for an agent and would likely be better split into focused sub-servers.

Completeness3/5

The tool surface is broad, covering search, stay management, applications, bookings, products, and help center. However, there are notable lifecycle gaps: no cancel booking, no delete stay, no delete application, and no way to update or delete a booking. These missing operations create potential dead ends for common workflows.

Resources