Skip to main content
Glama

Wingie Enuygun MCP

by com.enuygun

bus_search

Read-only

Search for bus routes between cities. Find available buses with schedules, pricing, seat availability, and operator information for intercity travel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adultsNoNumber of adult passengers
originYesDeparture city or terminal name (e.g., 'İstanbul', 'Ankara')
childrenNoNumber of child passengers (2-12 years)
destinationYesArrival city or terminal name (e.g., 'İzmir', 'Antalya')
return_dateNoReturn date in DD.MM.YYYY format (optional)
departure_dateYesDeparture date in DD.MM.YYYY format

TDQS

B3.4/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, but the description adds little beyond restating the search functionality. It does not mention dynamic data, rate limits, or other behavioral traits that annotations do not cover.

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 is two concise sentences with no redundancy. It efficiently conveys the tool's purpose and scope.

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?

Despite no output schema, the description hints at return fields (schedules, pricing, etc.). It is sufficiently complete for this search tool with good annotations and schema coverage.

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 describes all parameters adequately. The description adds minimal extra meaning (e.g., 'intercity travel'), so it meets the baseline but does not exceed.

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 verb 'search' and resource 'bus routes', specifies what information is returned (schedules, pricing, etc.), and distinguishes from sibling tools like car_search and flight_search by focusing on intercity bus travel.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide guidance on when to use this tool versus alternatives such as flight_search or car_search. No explicit context for selection or prerequisites is given.

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 toolsInspect
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