Skip to main content
Glama

jolly_search_hotels

Search Jolly hotels in a city. city: slug like "antalya", "istanbul", "bodrum". check_in/check_out: YYYY-MM-DD (both needed for prices). page: results page (20 hotels/page). hotel_name: optional name filter (4+ chars).

Instructions

Search Jolly hotels in a city. city: slug like "antalya", "istanbul", "bodrum". check_in/check_out: YYYY-MM-DD (both needed for prices). page: results page (20 hotels/page). hotel_name: optional name filter (4+ chars). Returns hotels with rating, concept, campaigns and prices.

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": "jolly_search_hotels"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYes
pageNo
check_inNo
check_outNo
hotel_nameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that prices only appear when both dates are supplied, that results are paginated at 20 hotels per page, that hotel_name needs 4+ characters, and what fields come back. Unstated behaviour such as authentication needs, sort order, or whether prices are per-room vs per-person keeps this below a 5.

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?

A single front-loaded sentence establishes purpose, then each parameter is addressed in a compact, consistently labelled clause followed by return fields. No filler and no repetition of structured data beyond the useful minimum.

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?

For a five-parameter search tool with an output schema present, the description covers formats, the price precondition, pagination, and the result shape. Environment-level details like auth or rate limits are missing, but nothing an agent needs in order to construct a correct call is absent.

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 description coverage is 0%, so the description must compensate, and it largely does: slug format with example values for city, YYYY-MM-DD format for the date pair, page semantics with page size, and a minimum length for hotel_name. Minor gaps remain, such as the default page value and whether dates are optional or merely required for pricing.

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?

"Search Jolly hotels in a city" states a specific verb and resource, and the city-scoped framing implicitly separates it from jolly_get_hotel (single hotel) and jolly_list_campaigns. It stops short of naming a sibling explicitly, but an agent can tell these apart from the description alone.

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?

Usage is implied rather than stated: the agent learns it needs a city slug and that check_in/check_out are both required for prices, which is genuine conditional guidance. There is no explicit statement of when to prefer jolly_get_hotel, nor any mention of exclusions or failure modes for an invalid city.

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