sozcu-mcp

sozcu_get_article

Retrieves the full text and metadata for a Sözcü article from its URL, including title, author, dates, description, image, and body content.

Instructions

Full text of one Sözcü article. article_url: the article's sozcu.com.tr URL (as returned by the headlines/latest/search tools, e.g. "https://www.sozcu.com.tr/10-meslek-grubu-icin-yesil-pasaport-meclis-yolunda-p376844"). Returns title, author, publish/modify dates, description, image and the full body text.

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": {
      "article_url": "<article_url>"
    },
    "name": "sozcu_get_article"
  }
}

Input Schema

Name	Required	Description	Default
`article_url`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A4.6/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 burden. It clearly indicates a retrieval operation and lists the returned fields, including full body text, but does not explicitly describe auth, error, or rate-limit behavior.

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?

The description is front-loaded with the purpose, then covers the parameter and return contents without unnecessary wording. The example URL earns its place by clarifying the expected format.

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

Completeness5/5

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

For a simple one-parameter article-fetch tool with an output schema, the description is complete enough: it states what is retrieved, where the URL comes from, and what content is returned. No critical context for calling the tool correctly is missing.

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 for the single article_url parameter. It does so effectively by explaining that the URL is a sozcu.com.tr article URL, noting where to obtain it, and providing a concrete example format.

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

Purpose5/5

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

The description states a specific resource and scope: the full text of exactly one Sözcü article. It also ties article_url back to the sibling headlines/latest/search tools, making the distinction from discovery tools clear.

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

Usage Guidelines4/5

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

It explains that article_url should come from the headlines, latest, or search tools, which gives clear usage context for a follow-up retrieval call. It does not explicitly state when not to use it or name an alternative retrieval tool, but the intended flow is clear.

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

Deploy Server