Skip to main content
Glama

eksisozluk_get_topic

Retrieve entries from an Ekşi Sözlük topic using its slug--id or exact title, with sorting by recent, popular, daily, or all-time and pagination controls.

Instructions

Entries of one topic.

topic: "slug--id" (e.g. "ankara--32788"), or an EXACT topic title (e.g. "ankara" — resolved via the site's /?q= redirect; a bare numeric id alone is not enough, and partial titles must go through eksisozluk_search_topics first). sort: "recent" (default), "popular" (şükela), "dailynice" (son 24 saat), "nice" (şükela tümü). page: entries page (10 per page); page_count is returned. limit: 1..10 entries returned. Each entry: entry_id, text, author, author_url, date, url.

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": {
      "topic": "<topic>"
    },
    "name": "eksisozluk_get_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
sortNorecent
limitNo
topicYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations present, the description carries the behavioral burden and does well: it discloses the /?q= redirect resolution path, the 10-entries-per-page pagination with page_count returned, and the 1..10 limit range. It omits failure behavior for an unresolved or nonexistent topic and any rate-limit or auth context, so it falls short of a 5.

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?

It is front-loaded with the purpose and return shape before the parameter-by-parameter detail, and nearly every clause carries operational information. The dense parenthetical chains around topic resolution are slightly tangled to parse but not wasteful.

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 four-parameter read tool with an output schema already present, the description supplies the parts structured data cannot: input formats, sort semantics, and pagination model. Remaining gaps are edge-case handling such as invalid topic or out-of-range page, which are minor given the output schema covers the response shape.

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

Parameters5/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 compensate entirely, and it does: topic format with examples and the exact-title escape hatch, sort with four enumerated values mapped to their Turkish meanings, page as a 10-per-page index, and limit constrained to 1..10. Every one of the four parameters gains meaning not present in the bare schema.

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 opens with a concrete statement of what is returned: the entries of a single topic, keyed by slug--id or exact title. It also differentiates itself from the sibling eksisozluk_search_topics by explicitly routing partial titles there, so an agent can tell the two apart without opening either schema, though the opening fragment lacks an explicit verb.

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

Usage Guidelines5/5

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

It specifies exactly which inputs are accepted ("slug--id" like "ankara--32788" or an EXACT title), gives the negative case (a bare numeric id is not enough), and names the alternative tool for partial titles. It also spells out the four sort modes and what each means, so selection between options is unambiguous.

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