Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP

hepsiemlak_scraper_turkey_real_estate_listings

Read-onlyIdempotent

Hepsiemlak Scraper - Turkey Real Estate Listings: Real-time structured data extraction feed for Hepsiemlak Scraper - Turkey Real Estate Listings.

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": "hepsiemlak_scraper_turkey_real_estate_listings"
  }
}

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.2/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 and network profile is covered. The description adds only the vague claim of "real-time" data, without disclosing freshness guarantees, rate limits, pagination behavior, or what a scrape returns — minimal value beyond structured fields.

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?

The single sentence is short, but it wastes most of its length repeating the tool title verbatim rather than front-loading useful scope or behavior. Brevity here comes from under-specification, not efficiency.

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?

For a scraper whose value depends on knowing what fields, geography, or listing types are returned, the description says nothing about output content, coverage, or data sources. With no output schema, the description should carry that burden and does not.

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?

With a single parameter and 100% schema description coverage, the schema already fully documents maxResults and its default. The description contributes nothing about pagination or result limits, so the baseline of 3 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 largely restates the tool name and title verbatim ("Hepsiemlak Scraper - Turkey Real Estate Listings"), which is tautological. The only added content is the generic phrase "real-time structured data extraction feed," which signals scraping/extraction but does not specify what listings data is returned or how it differs from sibling scrapers like bolha_scraper or njuskalo_scraper.

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 stated preconditions, and no mention of alternatives or exclusions. An agent must infer usage entirely from the tool name and the presence of other country/site-specific scrapers in the catalog.

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.