Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

turkey_hotels_explorer_ratings_amenities

Read-onlyIdempotent

Turkey Hotels Explorer - Ratings & Amenities: Real-time structured data extraction feed for Turkey Hotels Explorer - Ratings & Amenities.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "turkey_hotels_explorer_ratings_amenities"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. Beyond that, the description adds only the word "real-time," with no detail on data source, geographic scope (all 81 provinces? major tourist cities?), freshness, cost/latency, or how many records the feed can realistically return before truncation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler clutter, but that brevity comes from under-specification rather than discipline — the sentence spends its words repeating the title instead of front-loading scope or behavior.

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?

No output schema exists, so the description should describe the shape of returned records (hotel name, rating scale, amenity vocabulary) and any coverage caveats. Instead it says only "structured data extraction feed," leaving the agent unable to predict what fields or how much data come back from an open-world tool.

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?

There is a single optional parameter, maxResults, and it already has a 100% schema description ("Maximum number of records to return") plus a default of 10. The description adds no semantics of its own, so the baseline of 3 for full schema coverage applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name almost verbatim ("Turkey Hotels Explorer - Ratings & Amenities") and adds only the generic phrase "real-time structured data extraction feed." It never states a concrete verb such as retrieve, list, or look up, nor what entity is returned (hotels with ratings and amenity lists). An agent learns the domain but not the operation.

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?

There is no when-to-use guidance, no exclusions, and no named alternative among siblings such as hepsiemlak_scraper_turkey_real_estate_listings or turkey_car_rental_prices_city_airport_index. Usage is only implied by the topic in the name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources