Skip to main content
Glama
Sign In
FlightTicketMCP

FlightTicketMCP

by qqoqto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Getairportflights

getAirportFlights

Query all flights within 30 km of a specified airport using major codes like PEK, PVG, or CAN. Supports departure and arrival filtering.

Instructions

机场周边航班查询 - 查询指定机场周边30公里范围内的所有航班。支持主要机场代码如PEK、PVG、CAN等

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": {
      "airport_code": "<airport_code>"
    },
    "name": "getAirportFlights"
  }
}

Input Schema

NameRequiredDescriptionDefault
flight_typeNodeparture
airport_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses little beyond the geographic constraint. It says nothing about result volume, pagination, whether results are real-time, permission requirements, or the return shape for what could be a large result set.

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?

A single compact sentence that front-loads the resource and the spatial constraint followed by concrete code examples. No filler, though it is arguably too terse given the documentation gaps.

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

Completeness2/5

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

For a 2-parameter tool with no annotations and no output schema, the description should explain flight_type semantics and something about the return payload. It supplies only airport_code examples and a scope, leaving key calling details unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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. It partially does for airport_code by supplying example codes (PEK, PVG, CAN), but flight_type is never mentioned, leaving its allowed values (default 'departure') completely undocumented in both places.

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 states a specific verb (query), resource (flights), and scope (all flights within 30km of a specified airport), which is concrete and actionable. It does not, however, differentiate itself from the closely related sibling getFlightsInArea, so an agent cannot tell from the text alone which geographic tool to pick.

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?

The 30km airport-radius scope implies when the tool applies, giving implicit usage guidance. But there is no explicit when-not or any reference to the similar sibling getFlightsInArea, so the agent must infer the boundary.

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

Deploy Server

Other Tools