Skip to main content
Glama

Airsockfly

Search tours

search_tours
Read-onlyIdempotent

Search package holidays and tours to a destination, departing from a given city within a date window.

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": {
      "destination": "<destination>",
      "fromCity": "<fromCity>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "search_tours"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of offers to return, from 1 to 30. Default 10.
adultsNoNumber of adults.
endDateYesEnd date, YYYY-MM-DD.
fromCityYesCity the trip departs from.
startDateYesStart date, YYYY-MM-DD.
destinationYesHoliday destination: country, region or city.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety and determinism profile is covered. The description adds nothing beyond the purpose statement — no mention of how many offers come back, whether results are live supplier inventory (relevant given openWorldHint), currency, or what happens when nothing matches.

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 well-formed sentence that front-loads the verb and resource and then qualifies scope. No filler, no restatement of the title, nothing that could be cut.

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

Completeness3/5

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

With annotations covering the read-only/idempotent profile and a fully documented schema, the minimal description is workable for a 6-parameter search tool. However, with no output schema and no hint about result shape, offer counts, or pagination via limit, an agent must discover the return behavior by calling it.

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%, so the schema already documents all six parameters including limit bounds, adults, and date formats. The description only echoes destination, fromCity and the date window, and omits limit/adults entirely, so it adds no meaning beyond structured fields — the baseline of 3 applies.

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 gives a specific verb ('Search') and a specific resource ('package holidays and tours'), plus the three scoping dimensions (destination, origin city, date window). The resource domain implicitly separates it from search_cars/flights/hotels, but it never explicitly contrasts with those siblings.

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 only implied: an agent can infer this is the entry point for package/tour inventory given the required destination, origin and date window. There is no statement of when to prefer it over siblings like search_hotels or get_offer, and no prerequisites or exclusion cases.

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