Skip to main content
Glama
sozcu-mcp

sozcu-mcp

sozcu_search_news

Search today's Sözcü news by keyword, matching titles and summaries across the dated archive and homepage headlines. Returns up to 30 relevant articles per query when the site's own search is unavailable.

Instructions

Keyword search over today's Sözcü news: scans the dated all-news archive (up to 3 pages, 30 articles each) plus the homepage headlines, matching the keyword in titles and summaries. query: e.g. "ekonomi", "deprem", "dolar". limit 1..30. Note: the site's own /arama search redirects to the homepage, so this searches the current archive instead of a search backend.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does reasonably well: it discloses the scan depth (up to 3 pages, 30 articles each), which fields are matched (titles and summaries), and the caveat that the site's native search backend is unusable. It does not state result ordering, freshness window, or whether matching is case/substring-insensitive for Turkish characters.

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?

Front-loaded with the core operation and the corpus scope, followed by parameter hints and a closing caveat. Every sentence is relevant, though the /arama redirect note is somewhat tangential and the manual line breaks make it less scannable than it could be.

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 two-parameter search tool with an output schema already describing return values, the description supplies the essential operational context: corpus scope, matching fields, scan limits, and the limit range. Only result ordering and match-method details are missing, which are minor given the output schema's presence.

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%, but the description compensates: it gives query examples ('ekonomi', 'deprem', 'dolar') and, critically, the 'limit 1..30' bound, which the schema omits entirely (it only shows a default of 10). It stops short of describing the matching rule (substring vs. token, Turkish casing), leaving some semantic gap.

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 a specific verb and resource ('Keyword search over today's Sözcü news') and defines the corpus being scanned: the dated archive (up to 3 pages of 30) plus homepage headlines, with matching in titles and summaries. It does not, however, explicitly distinguish itself from the sibling 'sozcu_headlines', whose territory it partially overlaps by also scanning homepage headlines.

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 by the word 'search' and by the note that the site's own /arama endpoint redirects to the homepage, explaining why this tool exists. There is no explicit guidance on when to prefer it over sozcu_headlines or sozcu_latest, nor any stated exclusions.

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