Skip to main content
Glama
Sign In
iran-news-mcp

iran-news-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Latest news from a source

nw_latest
Read-onlyIdempotent

Retrieve newest headlines from a selected Persian news source, optionally filtered by category, to check current coverage and feed freshness.

Instructions

Return the newest headlines of one news source, optionally of one category.

Each item has title, url, published (UTC ISO), summary (plain text) and categories. stale: true means the feed's newest story is over 3 days old (some Digiato topic feeds go quiet). Use nw_list_sources for category slugs; use nw_search to look for a topic across sources.

Input Schema

NameRequiredDescriptionDefault
limitNoMax items (1-15), newest first.
sourceYesSource id such as mehr, tabnak or varzesh3 (see nw_list_sources).
categoryNoCategory slug from nw_list_sources, e.g. 'politics', 'economy', 'sports'. Empty = the source's main latest feed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.2
    • changedInput schema / properties / source / description
      Previous value: -"Source id: mehr, khabaronline, hamshahri, tabnak, zoomit or digiato (see nw_list_sources)."New value: +"Source id such as mehr, tabnak or varzesh3 (see nw_list_sources)."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the safety profile is free. The description still adds real value by disclosing the item shape and the non-obvious `stale: true` flag semantics (feed newest story over 3 days old), which cannot be inferred from structured fields.

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 purpose, then return fields, then the stale caveat, then routing hints — a sensible order with no filler. The second paragraph is slightly dense but every clause carries information.

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?

No output schema exists, so the description compensates by enumerating the returned fields and the timestamp format (UTC ISO). Combined with the stale-flag explanation and the source-slug routing, nothing an agent needs to call or interpret this tool is missing.

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 100%, so all three parameters are already documented, including the 1-15 limit range and category slug source. The description adds only a redundant pointer to nw_list_sources for slugs and says nothing extra about `limit` behavior.

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?

States a specific verb and resource ('Return the newest headlines') plus the scope ('one news source, optionally of one category'), which implicitly contrasts with the sibling nw_latest_all and with nw_search. An agent can tell what this returns without opening 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?

Explicitly routes the agent: nw_list_sources for category slugs, nw_search for cross-source topic lookup. The 'one news source' scope implies when to prefer nw_latest_all, but that alternative is never named and no when-not condition is stated.

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

Deploy Server

Other Tools