Skip to main content
Glama

Wingie Enuygun MCP

by com.enuygun
OverviewDiscussionsAdmin

car_search

Read-only

Search for car rental options between cities. Find available vehicles with pricing, specifications, and rental terms for specific dates and locations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination
tripNoTrip type: 'domestic' for local or 'international' for cross-border travel
limitNoNumber of results per page (maximum 20)
sort_byNoSort criteria: 'recommended', 'price_asc' for cheapest first, 'price_desc' for most expensive first, 'distance' for nearest first, 'review' for highest rated, or 'review_count' for most reviewed
driver_ageNoDriver age (minimum 18 years)
pickup_dateYesPickup date in YYYY-MM-DD format
pickup_timeNoPickup time in HH:MM format
dropoff_dateYesDrop-off date in YYYY-MM-DD format
dropoff_timeNoDrop-off time in HH:MM format
pickup_locationYesPickup city name (e.g., 'İstanbul', 'Ankara')
dropoff_locationYesDrop-off city name (e.g., 'İzmir', 'Antalya')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / sort_by
      Added value: +{
+  "description": "Sort criteria: 'recommended', 'price_asc' for cheapest first, 'price_desc' for most expensive first, 'distance' for nearest first, 'review' for highest rated, or 'review_count' for most reviewed",
+  "type": "string"
+}
  2. Added
  3. Removed
  4. Added
  5. Removed
  6. Changed3 schema fields changed
    • removedInput schema / properties / filters
      Removed value: -{
-  "description": "Additional filtering options for refining search results",
-  "type": "object"
-}
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results per page (maximum 50 for authenticated users)"New value: +"Number of results per page (maximum 20)"
    • removedInput schema / properties / sort_by
      Removed value: -{
-  "description": "Sort criteria: 'recommended', 'price_asc' for cheapest first, 'price_desc' for most expensive first, 'distance' for nearest first, 'review' for highest rated, or 'review_count' for most reviewed",
-  "type": "string"
-}
  7. Added
  8. Removed
  9. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to restate safety. It adds value by describing the output content (pricing, specifications, rental terms), but it does not disclose behaviors like pagination limits, result variability, or error conditions. Given the annotation coverage, this is adequate but not exceptional.

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?

Two sentences with no filler, front-loaded with the core purpose. The second sentence elaborates on expected results. It is appropriately concise for a search tool, though slightly generic.

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?

For a tool with 11 parameters and no output schema, the description gives a high-level view of the return content but omits nuances like sorting, pagination, or driver age requirements, which are only in the schema. It is sufficient for an agent to know the tool's purpose, but not deeply informative about edge cases or output structure.

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 all parameters are already documented in the input schema. The description only broadly mentions 'specific dates and locations', which aligns with required params but adds no new semantic detail beyond what the schema provides. Baseline of 3 is appropriate.

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 the resource 'car rental options', with specifics about between cities, dates, and locations. It also mentions the type of information returned (pricing, specifications, rental terms), making it distinct from sibling transport search tools like bus_search and flight_search.

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 usage for car rentals by naming the resource and scope, but it does not explicitly contrast with alternatives or state when not to use it. While the tool name and sibling context make the domain clear, there is no direct guidance on when to prefer this tool over others.

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