Skip to main content
Glama

Hostels in a city as listed on Hostelworld's public city

travel_hostelworld
Read-only

Hostels in a city as listed on Hostelworld's public city page (up to 30, Hostelworld's own order): name, address, coordinates, guest rating out of 10 with review count, lowest 'from' price per night as shown (currency depends on the visitor region) and property URL. Needs the continent, country and city as in Hostelworld URLs (e.g. europe / germany / berlin). No live availability for dates. Related tools on this server, for a different need: travel_numbeo when you need Numbeo cost-of-living prices for one city from its public; travel_agoda when you need top hotels in a city from Agoda's city guide page: about 10. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "continent": "<continent>",
      "country": "<country>",
      "city": "<city>"
    },
    "name": "travel_hostelworld"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity as in Hostelworld URLs, e.g. berlin, new-york, bangkok
limitNoHostels to return, 1 to 30 (default 30)
countryYesCountry as in Hostelworld URLs, e.g. germany, united-states, thailand
continentYesOne of europe, asia, africa, north-america, south-america, oceania, central-america

Output Schema

NameRequiredDescriptionDefault
cityNo
countNo
totalNo
sourceNo
countryNo
hostelsNo
checkedAtNo
continentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely new behavior: results capped at 30 in Hostelworld's own order, price currency varies by visitor region, prices are 'from' per-night figures rather than live rates. It also discloses the billing model ($0.002 per successful call via x402, failed calls not charged), which is important operational context. It stops short of describing failure modes for invalid continent/country/city slugs.

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?

Purpose and return fields are front-loaded in the first sentence, with constraints and alternatives following, and every clause carries information. Minor waste: 'for one city from its public' is truncated/awkward, and the limit of 30 is restated from the schema.

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?

An output schema exists, so return structure need not be explained, yet the description still summarizes the payload shape. Combined with the source constraints, ordering, pricing/currency caveat, cost model and sibling routing, an agent has everything needed to select and invoke it correctly.

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%, with per-parameter examples and the limit range already documented, so the schema does the heavy lifting. The description reinforces the URL-slug convention with a combined example ('europe / germany / berlin') but adds no semantics beyond what the schema carries, and the currency caveat is not tied to any parameter.

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?

States a specific resource (hostels in a city) from a specific source (Hostelworld's public city page) and enumerates the returned fields: name, address, coordinates, rating with review count, 'from' price, property URL. It also bounds the result set ('up to 30, Hostelworld's own order') and contrasts itself with travel_agoda ('top hotels in a city') and travel_numbeo, so an agent can distinguish it from siblings without opening a schema.

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?

Explicitly routes the agent: travel_numbeo for Numbeo cost-of-living prices, travel_agoda for top hotels from Agoda's city guide, each with the condition that selects it. It also states a negative constraint ('No live availability for dates'), which tells the agent when this tool will not satisfy a date-specific search.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources