Skip to main content
Glama

eksisozluk_debe

Retrieve yesterday’s top-voted Ekşi Sözlük entries grouped by topic, returning up to 12 topic groups for quick trend review.

Instructions

Yesterday's most-liked entries (debe), grouped by topic.

limit: 1..12 topic groups returned (the site lists ~10-12). Each group: topic_slug, topic_id, topic_title, topic_url, entries (usually 1 top entry per topic).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does a decent job: it discloses the return shape (grouped by topic, one top entry per topic typically) and the effective cap behavior, noting the site only lists ~10-12 groups so higher limits do not yield more. It omits freshness/auth/rate-limit context, e.g. when the 'yesterday' snapshot is regenerated, which matters for a daily-cached resource.

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?

Two short blocks, front-loaded with the one-line purpose followed by return-shape and limit detail. Every clause adds information an agent would otherwise have to discover by trial; there is no filler or restatement of the name.

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

Completeness4/5

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

For a single-optional-parameter read tool with an output schema, this is nearly complete: purpose, grouping, and limit semantics are all present, and the return fields are described even though the output schema already covers them. The only meaningful gap is temporal context about the daily snapshot, which is minor for such a simple tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the schema exposes only a bare integer with default 10, so the description must compensate and largely does: it gives the valid range 1..12 and clarifies that the unit is topic groups, not entries, which is exactly the ambiguity an agent would otherwise guess wrong on. It could have restated the default and the behavior when limit exceeds the available group count, but the essential semantics are covered.

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

Purpose4/5

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

The description names a specific resource and its scope: yesterday's most-liked entries, grouped by topic, with the local term 'debe' for disambiguation. That is far more specific than a restatement of the tool name. It stops short of explicitly contrasting itself with siblings such as eksisozluk_trending or eksisozluk_channel_topics, leaving the agent to infer that this is a fixed daily snapshot rather than a live ranking.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: 'yesterday's most-liked' tells an agent this is the right tool for a daily top-entries digest, and 'grouped by topic' implies it is not the tool for fetching a single topic's entries. There is no explicit when-to-use/when-not statement and no named alternative for cases like 'current trending' or 'search by keyword'.

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