Skip to main content
Glama

eksisozluk_channel_topics

Fetch paginated topics from a chosen Ekşi Sözlük channel to browse category discussions with adjustable page and limit.

Instructions

Topics of one eksisozluk.com channel.

channel: e.g. "spor", "siyaset", "iliskiler", "yasam", "seyahat", "muzik", "tv", "haber", "bilim", "edebiyat", "kripto". page: list page (50 topics per page). limit: 1..50 topics returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channel": "<channel>"
    },
    "name": "eksisozluk_channel_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
channelYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 it does disclose a genuinely useful trait beyond the schema: pagination at 50 topics per page. It does not state that the operation is read-only, does not mention auth or rate limits, or what happens if page exceeds the available range; the output schema covers the return shape, which limits the gap.

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

Conciseness4/5

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

The purpose statement is front-loaded in one short sentence, followed by per-parameter notes; almost nothing is wasted. The long inline list of channel examples makes the middle sentence dense and slightly awkward to scan, but the structure remains serviceable.

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 three-parameter read tool with an output schema, the description covers the resource, all three parameters, and pagination behavior. What remains uncovered are the read-only nature of the call and edge-case behavior for invalid channels or out-of-range pages, which are real but modest gaps given the output schema handles return values.

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 description coverage is 0%, so the description must carry parameter meaning, and it does: channel is illustrated with eleven concrete example values, page is defined as the list page with an explicit 50-per-page size, and limit is bounded to 1..50. It omits the schema defaults (page=1, limit=20) and doesn't say how limit interacts with the 50-per-page size, which keeps it short of a 5.

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 states the specific resource and scope: topics belonging to a single eksisozluk.com channel, with concrete channel examples. It is clear what the tool returns, but it never contrasts itself with siblings like eksisozluk_search_topics or eksisozluk_trending, leaving the agent to infer the boundary.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives are named. Usage is only weakly implied by the channel/page/limit framing, so an agent must guess whether this or eksisozluk_search_topics is the right entry point for browsing topics.

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