Skip to main content
Glama

Top hotels in a city from Agoda's city guide page: about 10

travel_agoda
Read-only

Top hotels in a city from Agoda's city guide page (no dates needed): about 10 properties with Agoda hotel ID, name, star rating, area, amenities (Wi-Fi, parking, breakfast, pool …), review score out of 10 with its label and number of reviews, a recent guest quote, average price per night with currency, and the Agoda hotel link. The city is Agoda's URL slug, e.g. bangkok-th, tokyo-jp, bali-id, london-gb. Related tools on this server, for a different need: travel_hostelworld when you need Hostels in a city as listed on Hostelworld's public city; travel_kayak when you need KAYAK flight route overview between two city or airport. 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": {
      "city": "<city>"
    },
    "name": "travel_agoda"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesAgoda city slug: <city>-<2-letter country>, e.g. bangkok-th, singapore-sg, paris-fr
limitNoHotels, 1 to 20 (default 20)

Output Schema

NameRequiredDescriptionDefault
cityNo
countNo
titleNo
sourceNo
resultsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, openWorldHint), so the description's real contribution is the return shape (IDs, star rating, amenities, review score/label/count, guest quote, price+currency, link) and the billing behavior: $0.002 per successful call via x402, with failed calls not charged. That cost/failure disclosure is genuinely useful context beyond annotations, though latency and rate limits are unaddressed.

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?

Front-loads the core purpose and the 'no dates needed' constraint in the first clause, then the slug convention, then cost. The long field enumeration with '…' is somewhat padded, and the 'Related tools on this server, for a different need' phrasing is clunky, but no sentence is entirely wasted.

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?

An output schema exists, so the field list is redundant but harmless; the description still covers what an agent needs to call it correctly – city slug format with examples, approximate result volume, and total cost. Only the limit/default relationship and the choice among competing hotel sources remain under-explained.

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 coverage is 100% and both parameters are documented in-schema, so baseline is 3. The description repeats the city slug convention already present in the schema and adds no syntax or edge-case guidance for 'limit'; in fact 'about 10 properties' sits in mild tension with the schema's default of 20 without explaining the relationship.

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 verb+resource+source: 'Top hotels in a city from Agoda's city guide page', with a concrete result count ('about 10 properties') and an explicit scope qualifier ('no dates needed'). It also names two siblings it is not (travel_hostelworld for hostels, travel_kayak for flights), so an agent can distinguish it without opening schemas.

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?

Gives clear usage context ('no dates needed') and explicitly routes two alternative needs to travel_hostelworld and travel_kayak. It does not, however, distinguish itself from the many other hotel-price siblings (travel_booking_com_hotels, travel_google_hotels_price, travel_trivago), leaving the agent to infer which hotel source to prefer.

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