Skip to main content
Glama
iran-news-mcp

iran-news-mcp

by sepehr071

Read a news article

nw_article
Read-onlyIdempotent

Fetch the full body text of one news article from a URL and return it in parts for long stories, allowing agents to read complete article content.

Instructions

Fetch one article page and return its full body text, split into parts for long stories.

Photo and video items often have no body text. If parts > 1, call again with part=2, ...

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": {
      "url": "<url>"
    },
    "name": "nw_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesArticle `url` from a listing tool.
partNoPart number (6000 chars each).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / part / description
      Previous value: -"Part number for long articles (6000 characters each); see `parts`."New value: +"Part number (6000 chars each)."
    • changedInput schema / properties / url / description
      Previous value: -"Article url from nw_latest / nw_search / nw_latest_all (from any listed source)."New value: +"Article `url` from a listing tool."
  2. Changed1 schema field changedv0.2.2
    • changedInput schema / properties / url / description
      Previous value: -"Article url from nw_latest / nw_search / nw_latest_all (one of the six sites)."New value: +"Article url from nw_latest / nw_search / nw_latest_all (from any listed source)."
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), and the description adds real behavior beyond them: the response is full body text chunked into parts, and photo/video items frequently return no body text — an important empty-result expectation. It omits failure modes such as paywalls, timeouts, or rate limits.

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?

Three short sentences with no filler: purpose first, the empty-body caveat second, the pagination loop last. The most important information is front-loaded.

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?

With no output schema supplied, the description does needed work by describing the return (full body text, a `parts` count) and the empty-body case. It still leaves the exact response shape only loosely implied, which is a minor gap for a two-parameter read tool.

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 100%, so the schema already documents both parameters, but the description adds meaning by linking the `part` parameter to a `parts` count in the response and prescribing the re-call pattern. That is genuine semantic value beyond the schema's "Part number (6000 chars each)".

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?

"Fetch one article page and return its full body text" gives a concrete verb (fetch) and resource (one article page), and the singular "one article" cleanly separates it from the listing-style siblings (nw_latest, nw_search, nw_list_sources). An agent can distinguish its role without inspecting the schema.

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 establishes the call context by tying the required url to "from a listing tool" (reinforced in the schema) and gives an explicit follow-up rule for pagination: "If parts > 1, call again with part=2, ...". It does not name a specific alternative tool or state when not to use this one, which keeps it short of a 5.

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