Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

eksi_sozluk_scraper_entries_trending

Read-onlyIdempotent

Eksi Sozluk Scraper - Entries & Trending: Real-time structured data extraction feed for Eksi Sozluk Scraper - Entries & Trending.

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

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, openWorldHint, idempotentHint and destructiveHint=false, so safety is covered. The only added behavioral claim is 'real-time', which is unqualified and left unexplained (no freshness window, pagination, rate limits, or result-shape information). Given annotations do the heavy lifting, the description contributes little beyond a marketing phrase.

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 short and front-loaded, but the single sentence is largely wasted repetition of the tool's own title rather than substantive information. Brevity here comes from under-specification rather than disciplined editing.

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 simple one-parameter tool this could be near-complete, but with no output schema the description gives no indication of what records look like (fields per entry, trending ordering, author/content metadata). An agent cannot predict the response shape or confirm the tool matches its need before invoking it.

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 schema description coverage is 100%, so the schema already documents its meaning and default of 10. The description adds nothing about the parameter, but with full coverage the baseline of 3 is appropriate.

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 and title almost verbatim ('Eksi Sozluk Scraper - Entries & Trending ... for Eksi Sozluk Scraper - Entries & Trending'), adding only the vague label 'real-time structured data extraction feed'. It never states what an 'entry' is, what 'trending' measures, or which site sections are covered, so it does not distinguish this tool's actual output from any other scraper sibling.

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 mention of the many sibling scrapers or when this one should be preferred over an alternative Eksi Sozluk or Reddit/Twitter source. An agent must infer usage entirely from the tool 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