Skip to main content
Glama

geoagentic

by app.geoagentic
OverviewDiscussionsAdmin

hostel-prices

Live hostel and budget accommodation prices from Hostelworld for any city worldwide. USE FOR:

  • "What are the cheapest hostels in Paris next week?"

  • "Find dorm beds in Bangkok for 3 nights from July 10"

  • "Compare hostel prices in Ljubljana vs Belgrade"

  • Budget travel planning, accommodation cost context, backpacker routing RETURNS: Per-property dorm and private room prices per night, guest ratings, free cancellation flag, and summary stats (floor/avg/top price). CRITICAL INSTRUCTIONS FOR AGENT:

  • Always pass date as YYYY-MM-DD format.

  • currency defaults to EUR.

  • Use summary.floor for "cheapest" queries, summary.average for general cost context.

  • free_cancellation=true properties are preferable for uncertain itineraries.

Input Schema

NameRequiredDescriptionDefault
cityYesCity name, e.g. Ljubljana, Paris, Bangkok, New York
dateYesCheck-in date in YYYY-MM-DD format
guestsNoNumber of guests, e.g. 22
nightsNoNumber of nights to stay, e.g. 35
currencyNoCurrency code: EUR, USD, GBP, etc.EUR

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "date",
-  "city"
-]New value: +[
+  "city",
+  "date"
+]
  2. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "city",
-  "date"
-]New value: +[
+  "date",
+  "city"
+]
  3. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "date",
-  "city"
-]New value: +[
+  "city",
+  "date"
+]
  4. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "city",
-  "date"
-]New value: +[
+  "date",
+  "city"
+]
  5. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "date",
-  "city"
-]New value: +[
+  "city",
+  "date"
+]
  6. Added

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description fully addresses behavior: it returns per-property prices, guest ratings, free cancellation flag, and summary stats. The critical instructions add transparency on formatting and best practices. No contradictions.

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?

The description is well-structured with clear sections (USE FOR, RETURNS, CRITICAL INSTRUCTIONS). It is front-loaded with the main purpose and each sentence adds value. No redundant or missing information.

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

Completeness5/5

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

Given 5 parameters (2 required), no output schema, and no annotations, the description is complete. It explains the return structure (dorm/private prices, ratings, cancellation flag, stats) and parameter usage. An agent can confidently invoke the tool with this information.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value beyond the schema by explaining how to interpret derived fields (summary.floor for cheapest, summary.average for general context) and emphasizing date format and default currency. This directly helps an agent use parameters correctly.

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?

The description clearly states the tool's purpose: 'Live hostel and budget accommodation prices from Hostelworld for any city worldwide.' It uses a specific verb (get/prices) and resource (hostel prices), and distinguishes from sibling tools which are unrelated (geo, events, etc.). No ambiguity.

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?

The description provides explicit USE FOR examples and critical instructions (date format, currency default, meaning of summary fields, free_cancellation preference). This gives clear guidance on when and how to use the tool, with no missing exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All geoagentic 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