Wingie Enuygun MCP

flight_search

Read-only

Search for flights between cities and airports. Find available flights with schedules, pricing, airline information, and seat availability for domestic and international travel.

Input Schema

TableJSON Schema

Name	Required	Description
`adults`	No	Number of adult passengers
`origin`	Yes	Departure city or airport name (e.g., 'İstanbul', 'Ankara')
`infants`	No	Number of infant passengers (0-2 years)
`children`	No	Number of child passengers (2-12 years)
`cabin_class`	No	Cabin class (ECONOMY, BUSINESS, PREMIUM_ECONOMY, FIRST)
`destination`	Yes	Arrival city or airport name (e.g., 'İzmir', 'Antalya')
`return_date`	No	Return date in DD.MM.YYYY format
`direct_flight`	No	Only direct flights
`departure_date`	Yes	Departure date in DD.MM.YYYY format

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that the tool returns schedules, pricing, and availability, but does not disclose additional behavioral traits such as authentication requirements, rate limits, or how data freshness is handled. With annotations covering the main safety profile, the description provides modest added context.

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?

The description consists of two concise sentences, immediately indicating the tool's action and scope. No unnecessary information or repetition.

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?

Given 9 parameters (3 required) and no output schema, the description is brief. It does not explain return value format, pagination, error behavior, or how to interpret results. The schema descriptions cover parameter syntax, but the description lacks completeness for a full understanding of tool usage.

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 parameters. The description adds a general note about domestic/international travel and the type of data returned, but does not provide additional semantic meaning for individual parameters beyond what the schema offers.

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?

The description clearly states the tool searches for flights between cities/airports, listing specific details like schedules, pricing, airline info, and seat availability. It distinguishes itself from sibling tools (bus_search, car_search, hotel_search) by focusing exclusively on flights.

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 description implies use for flight searches but lacks explicit guidance on when to use this tool versus alternatives like bus_search or car_search. No when-not-to-use or prerequisites are mentioned.

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

All Wingie Enuygun MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation5/5

Each tool targets a distinct combination of travel vertical (flight, bus, car, hotel) and action (search, allocate, weather, room details). The weather forecast tools are separated by transport mode with different condition types, so an agent can reliably choose the right one.

Naming Consistency4/5

Most tools follow a clear resource_action pattern such as bus_search, flight_allocate, and hotel_weather_forecast. Minor deviations are hotel_room_detail, which uses a noun phrase, and mcp_enuygun_ping, which breaks the pattern but is a standard connectivity check.

Tool Count5/5

Twelve tools is a reasonable size for a multi-vertical travel booking server covering flights, buses, cars, hotels, and weather. Each vertical has search and weather coverage, with allocation and detail tools where most relevant.

Completeness3/5

Flight and car searches have matching allocation tools, but bus_search has no bus allocation/booking tool and hotel_search/hotel_room_detail have no hotel booking allocation tool. The core search and planning surface is present, but the booking lifecycle is inconsistent across verticals.

Resources

Need Help?