Skip to main content
Glama

JpBiz Japan Business Trip Planner

Flight search link (Trip.com)

flight_search_link
Read-onlyIdempotent

Build a Trip.com flight search link with route, dates, passengers and cabin pre-filled, for a business trip to or from Japan. Returns a link only: no fares, no booking. Give the user the link exactly as returned, with the disclaimer.

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": {
      "origin": "<origin>",
      "destination": "<destination>",
      "departDate": "<departDate>"
    },
    "name": "flight_search_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
cabinNoeconomy
adultsNoNumber of adult passengers, 1-9.
originYesDeparture airport or city IATA code, e.g. PVG or SHA (Shanghai), PEK (Beijing), CAN, SZX, HKG, TPE, ICN, SIN, BKK.
currencyNoCurrency shown on Trip.com. Default: CNY for zh, USD for en, JPY for ja.
languageNoLanguage of the reply (and of the partner page for links): zh = Simplified Chinese, en = English, ja = Japanese. Use the user's language.zh
departDateYesOutbound date, YYYY-MM-DD.
returnDateNoReturn date, YYYY-MM-DD. Omit for a one-way trip.
destinationYesArrival IATA code. Japan: TYO (all Tokyo airports), HND, NRT, OSA (all Osaka airports), KIX, NGO, FUK, CTS, OKA, SDJ, HIJ.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world behavior, so the description's job is to add operational context — and it does: the tool yields no fares and performs no booking, and the agent must relay the link verbatim with a disclaimer. It does not specify whether the disclaimer text is supplied by the tool or must be composed, which leaves a real gap for the calling agent.

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?

Three short sentences, front-loaded with the purpose and followed by the output contract and the relaying instruction. No filler.

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?

Eight parameters at 88% schema coverage with no output schema — the description correctly discloses that the return value is a bare link and adds the verbatim-relay requirement. Only the disclaimer specifics and the Japan-origin/destination constraint implied by the examples are left 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 88% and the schema already documents IATA codes, date formats, defaults and enums in detail. The description only restates the field list (route, dates, passengers, cabin) without adding format or constraint details beyond it, so the baseline of 3 applies.

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 ('Build a Trip.com flight search link') plus what gets pre-filled, and the Japan business-trip scope makes it unmistakably distinct from hotel_search_link and generate_itinerary.

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?

Clearly frames the use case (business trip to/from Japan) and sets a hard expectation boundary with 'Returns a link only: no fares, no booking.' It never names an alternative tool or says when to prefer one, so it stops short of full routing guidance.

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