Skip to main content
Glama

eksisozluk_search_topics

Find Ekşi Sözlük topics by searching partial Turkish titles and return matching titles, slugs, IDs, entry counts, and URLs with pagination and result limits.

Instructions

Search topic titles on eksisozluk.com (partial matches welcome).

query: Turkish search text (e.g. "ankar"). page: results page (50 topics per page). limit: 1..50 topics returned. Each topic: title, slug, topic_id, entry_count, 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": {
      "query": "<query>"
    },
    "name": "eksisozluk_search_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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. It usefully discloses pagination behavior ('50 topics per page') and the returned record shape, but says nothing about rate limits, auth requirements, empty-result handling, or whether the whole site is searched versus a subset. The pagination detail is real added value; the operational gaps keep it at 3.

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 is front-loaded in a single clause, followed by compact parameter notes and a return-field list. No filler or repetition, though the enumerated return fields duplicate what the existing output schema already provides.

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-only search with an output schema present, the description covers purpose, matching semantics, pagination, and limits — enough to invoke it correctly. Missing only routing guidance against siblings and any failure-mode notes.

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?

Schema description coverage is 0%, so the description must compensate for all three parameters. It does explain query ('Turkish search text') and limit ('1..50 topics returned'), which are genuinely informative, and clarifies that page maps to 50-per-page results. However, defaults (page=1, limit=20) and the 'Turkish' language constraint are the only real additions, so it earns a solid but not exceptional 3.

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 verb and resource — 'Search topic titles on eksisozluk.com' — and adds the matching semantics ('partial matches welcome'), which is the key distinction from a fetch-by-slug tool like eksisozluk_get_topic. It stops short of explicitly naming a sibling to route away from, so it lands at 4 rather than 5.

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?

'Search topic titles' plus 'partial matches welcome' implies the use case (fuzzy title lookup when you don't have an exact slug), but there is no explicit statement of when to prefer this over eksisozluk_get_topic or eksisozluk_channel_topics. Usage is inferable rather than stated.

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