Skip to main content
Glama
Sign In

GMPSignal Real-Time Intelligence MCP

by io.github.xpayrcom
OverviewDiscussionsAdmin

turkey_hotels_explorer_ratings_amenities

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 structured items to extract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses almost nothing. The phrase "real-time structured data extraction feed" hints at live scraping but says nothing about auth, rate limits, cost, failure modes, or what gets returned per hotel.

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

Conciseness2/5

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

It is a single short sentence, but nearly every word is a verbatim echo of the tool name, so no sentence earns its place. Brevity here reflects under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and no explanation of the returned record fields or how hotels are scoped, an agent has nothing to call this confidently on. The description should at minimum explain what a "structured item" contains and which hotels are covered.

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 parameter, maxResults, and the schema covers it at 100% with its own description and default. The description adds no semantics beyond the schema, so the baseline of 3 for fully covered parameters 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 only restates the name: "Turkey Hotels Explorer - Ratings & Amenities: Real-time structured data extraction feed for Turkey Hotels Explorer - Ratings & Amenities." It never says what ratings (stars? guest scores?) or which amenities are returned, and gives no clue how the target hotel set is chosen. The topical name does the work, not the description.

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

Usage Guidelines1/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 prerequisites, and no mention of any alternative tool. An agent cannot tell from this text whether this is a scraping feed, a static dataset, or how it differs from sibling Turkey data tools.

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

All GMPSignal Real-Time Intelligence 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