Skip to main content
Glama
iran-news-mcp

iran-news-mcp

by sepehr071

Tech news (Digiato, Zoomit)

nw_tech_news
Read-onlyIdempotent

Fetch recent technology news stories and long summaries from Digiato and Zoomit, filtered by topic, category, or source, for answering tech questions.

Instructions

Return the newest technology news (phones, laptops, AI, gadgets, apps, crypto, cars, security, games) with long summaries.

Use first for any technology question. A topic scans the latest 50 Digiato stories (Zoomit: 300); scanned is how many were searched, so if count is low try a shorter topic or source='both'. Items add categories and author; replies up to ~25 KB.

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_tech_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax stories (1-30), newest first.
topicNoKeywords, all must match title/summary; Persian or brand names. For a broad subject use `category`. Empty = no filter.
sourceNodigiato (default, richest summaries and paging), zoomit, or both merged by time.digiato
categoryNoTech slug: Digiato mobile, apps, ai, gadgets, hardware, laptop, crypto, internet, security, reviews, car, business, buying-guide, science; Zoomit adds apple, samsung, gaming, space, software-news, ... (nw_list_sources has all). Empty = all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • changedInput schema / properties / category / description
      Previous value: -"Tech topic slug. Digiato: mobile, apps, ai, gadgets, hardware, laptop, crypto, internet, security, reviews, car, business, buying-guide, science. Zoomit adds apple, samsung, gaming, space, software-news, ... (nw_list_sources has all). Empty = everything."New value: +"Tech slug: Digiato mobile, apps, ai, gadgets, hardware, laptop, crypto, internet, security, reviews, car, business, buying-guide, science; Zoomit adds apple, samsung, gaming, space, software-news, ... (nw_list_sources has all). Empty = all."
    • changedInput schema / properties / limit / description
      Previous value: -"Max stories (1-30), newest first. Use 20-30 for a roundup."New value: +"Max stories (1-30), newest first."
    • changedInput schema / properties / topic / description
      Previous value: -"Keywords; every word must appear in the title or summary. Persian or brand names. Empty = no filter."New value: +"Keywords, all must match title/summary; Persian or brand names. For a broad subject use `category`. Empty = no filter."
  2. Addedv0.2.2

TDQS

A4/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 genuinely new behavioral facts: topic scans only the latest 50 Digiato / 300 Zoomit stories, the response reports `scanned` so the agent can self-diagnose, and replies cap around 25 KB. It also discloses that items carry `categories` and `author`. Missing only how pagination works despite hinting at 'paging' for digiato.

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 purpose, then operational detail, with zero filler sentences. The middle sentence is dense and slightly run-on across the `topic`/`scanned`/`count` advice, but every clause carries actionable 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 carries return-value burden and does so by naming the fields added to items (`categories`, `author`) and the `scanned` counter, plus a response-size ceiling. For a four-optional-parameter read tool this is nearly sufficient; only pagination behavior remains underspecified.

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 baseline would be 3, but the description adds real meaning: it explains that `topic` is a bounded scan of recent stories rather than a full-archive search, that low `count` is a signal to rephrase, and that source='both' merges by time. This goes beyond the schema's per-field text even though `limit` and `category` get no extra treatment.

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?

States a specific verb and resource (return the newest technology news) and enumerates the topical coverage (phones, laptops, AI, crypto, etc.), so the agent knows exactly what comes back. It also positions itself as the entry point versus the other news tools with 'Use first for any technology question', though it never names the siblings (nw_search, nw_latest, nw_article) it is being preferred over.

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?

Gives clear routing guidance ('Use first for any technology question') plus a concrete fallback procedure: if `count` is low, shorten the `topic` or switch to source='both'. It stops short of stating when NOT to use it or explicitly naming which sibling to pick instead for article bodies or full search.

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