Skip to main content
Glama
iran-news-mcp

iran-news-mcp

by sepehr071

Latest news across sources

nw_latest_all
Read-onlyIdempotent

Fetch current headlines from all or selected Iranian news sources, merged and sorted by time for a quick overview; filter by category such as economy or sports.

Instructions

Return the newest headlines from every source (or the chosen ones), merged and sorted by time.

Use for a general overview; pass a common category slug such as 'economy' or 'sports' to narrow it (not sources, which drops other groups). Not for technology questions (use nw_tech_news). Sources lacking the category appear under errors.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nw_latest_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourcesNoSource ids to include. Empty = all sources.
categoryNoSlug from nw_list_sources, e.g. 'economy', 'sports'. Empty = main feed.
per_sourceNoItems (1-2) per source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / category / description
      Previous value: -"Category slug from nw_list_sources, e.g. 'politics', 'economy', 'sports'. Empty = the source's main latest feed."New value: +"Slug from nw_list_sources, e.g. 'economy', 'sports'. Empty = main feed."
    • changedInput schema / properties / per_source / description
      Previous value: -"Items (1-2) taken from each source before merging."New value: +"Items (1-2) per source."
  2. Changed3 schema fields changedv0.2.2
    • changedInput schema / properties / per_source / description
      Previous value: -"Items (1-3) taken from each source before merging."New value: +"Items (1-2) taken from each source before merging."
    • changedInput schema / properties / per_source / maximum
      Previous value: -3New value: +2
    • changedInput schema / properties / sources / description
      Previous value: -"Source ids to include. Empty = all six."New value: +"Source ids to include. Empty = all sources."
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: results are merged and time-sorted across sources, and sources lacking the requested category surface under `errors` rather than failing. Missing only details like result count limits or ordering ties, so 4 rather than 5.

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 action, then usage, then the exclusion, then the edge case — a sensible priority order with little waste. The stray line break and compressed parenthetical slightly hurt readability, but every sentence carries information.

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, the description steps in to explain that results are merged and time-sorted and that per-source failures land in `errors`, which is exactly the return-shape knowledge an agent needs. Combined with annotation coverage and full schema descriptions, the definition is callable without further inference; only per_source limits beyond the schema and result volumetrics are left implicit.

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 baseline is 3, but the description adds genuine meaning: it warns that `sources` is the wrong lever for category narrowing because it drops other groups, which is a semantic trap the schema text does not disclose. It also reinforces the category slug vocabulary ('economy', 'sports') and points to nw_list_sources as the slug source.

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 aggregation behavior ("merged and sorted by time") and the scope switch ("every source (or the chosen ones)"). It explicitly contrasts itself with the sibling nw_tech_news, so an agent can pick between them without opening a schema.

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

Usage Guidelines5/5

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

Provides an explicit use case ("general overview"), a narrowing instruction with a concrete example slug, a trap warning ("not `sources`, which drops other groups"), and an explicit exclusion routing to nw_tech_news. When-to-use, when-not-to-use, and the alternative are all named.

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