Skip to main content
Glama
Sign In

BayDeep — The e-commerce plugin for AI agents

by io.github.MeshTok
OverviewDiscussionsAdmin

flight_search

Search FLIGHT FARES in the catalog (Aviasales/Travelpayouts partners, fares refreshed daily). Filter by origin/destination IATA code (e.g. PEK, JFK, SIN) and optional departure date (YYYY-MM-DD). Items sorted by price; book_url is ALREADY affiliate-attributed — link the user straight to it (no convert_link needed). Works WITHOUT any API key. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flight_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNodeparture date YYYY-MM-DD (optional)
originNoorigin IATA code, e.g. PEK
page_sizeNo
destinationNodestination IATA code, e.g. SIN

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?

With no annotations, the description carries the full burden and does well: it discloses data freshness (fares refreshed daily), result ordering (sorted by price), the affiliate-attribution side effect on book_url, that no API key is required, and that it is read-only. It stops short of describing pagination behavior or what a result item contains beyond book_url.

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-loaded with the action and the key routing hint (no convert_link needed) before secondary details. Slightly dense with parentheticals and ALL-CAPS emphasis, but no sentence is 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?

For a 4-parameter read-only search with no annotations and no output schema, the description covers provenance, filtering, ordering, and the affiliate link well enough to call correctly. The notable omission is page_size and pagination semantics, which the agent must infer from the schema's default and maximum alone.

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 75%, so origin, destination, and date are already documented in the schema and the description largely restates their formats (IATA, YYYY-MM-DD). The one undocumented parameter, page_size, is never mentioned in the description, so it does not compensate for the remaining gap.

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 and resource ('Search FLIGHT FARES in the catalog') and adds the data provenance (Aviasales/Travelpayouts partners). It also distinguishes itself from a sibling by noting book_url is already affiliate-attributed so convert_link is unnecessary.

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 conditions for use: filter by origin/destination IATA with an optional departure date, and skip convert_link. It does not explicitly contrast with search_products or shelf_search, so the boundary against the non-flight search siblings is left implicit.

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

All BayDeep — The e-commerce plugin for AI agents 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