Skip to main content
Glama

Wingie Enuygun MCP

by com.enuygun
OverviewAdmin

hotel_search

Read-only

Search for hotels in a destination with comprehensive filtering and pagination options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (default: 1)
limitNoNumber of results per page (max 30, default: 10)
roomsNoNumber of rooms needed (default: 1)
adultsNoNumber of adult guests (minimum 1, default: 1)
localeNoLocale code (default: 'tr_TR')
childrenNoAges of children as list (e.g., [8, 12] for 8 and 12 year olds)
currencyNoCurrency code (default: 'TRY')
nationalityNoNationality code (default: 'tr')
check_in_dateYesCheck-in date in DD.MM.YYYY format (e.g., '15.08.2025')
check_out_dateYesCheck-out date in DD.MM.YYYY format (e.g., '17.08.2025')
destination_nameYesDestination city name (e.g., 'İstanbul', 'Antalya', 'Bodrum')

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Changed11 schema fields changed
    • changedInput schema / properties / adults / description
      Previous value: -"Number of adult guests"New value: +"Number of adult guests (minimum 1, default: 1)"
    • changedInput schema / properties / check_in_date / description
      Previous value: -"Check-in date in DD.MM.YYYY format"New value: +"Check-in date in DD.MM.YYYY format (e.g., '15.08.2025')"
    • changedInput schema / properties / check_out_date / description
      Previous value: -"Check-out date in DD.MM.YYYY format"New value: +"Check-out date in DD.MM.YYYY format (e.g., '17.08.2025')"
    • changedInput schema / properties / children / description
      Previous value: -"Ages of children (e.g., [8, 12])"New value: +"Ages of children as list (e.g., [8, 12] for 8 and 12 year olds)"
    • addedInput schema / properties / currency
      Added value: +{
+  "description": "Currency code (default: 'TRY')",
+  "type": "string"
+}
    • changedInput schema / properties / destination_name / description
      Previous value: -"Destination city name (e.g., 'İstanbul', 'Antalya')"New value: +"Destination city name (e.g., 'İstanbul', 'Antalya', 'Bodrum')"
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Number of results per page (max 30, default: 10)",
+  "type": "integer"
+}
    • addedInput schema / properties / locale
      Added value: +{
+  "description": "Locale code (default: 'tr_TR')",
+  "type": "string"
+}
    • addedInput schema / properties / nationality
      Added value: +{
+  "description": "Nationality code (default: 'tr')",
+  "type": "string"
+}
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Page number for pagination (default: 1)",
+  "type": "integer"
+}
    • changedInput schema / properties / rooms / description
      Previous value: -"Number of rooms"New value: +"Number of rooms needed (default: 1)"
  6. Added
  7. Removed
  8. First observed

TDQS

B3.4/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, so the description's mention of 'search' is consistent but adds minimal value. It hints at filtering and pagination but does not elaborate on rate limits, data freshness, or other behavioral traits.

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?

Single sentence, front-loaded with the main action, no redundant words. Efficient and to the point.

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?

With 11 parameters and no output schema, the description should hint at return value structure or common usage patterns. It does not explain what the response contains (e.g., hotel details, prices), leaving gaps for an AI agent.

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 baseline 3. The description adds only a generic 'comprehensive filtering and pagination options' without providing additional meaning beyond the schema's parameter descriptions.

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', the resource 'hotels', and the scope 'in a destination with comprehensive filtering and pagination options', effectively distinguishing from sibling tools like bus_search, flight_search, etc.

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?

No guidance on when to use this tool versus alternatives like hotel_room_detail, nor any mention of when not to use it. The description lacks decision-making context.

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.

Resources