Skip to main content
Glama
danmarce

news-mcp

by danmarce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

news_by_topic

Read-only

Search recent news headlines and summaries by keyword, newest first, with optional lookback days and language filter.

Instructions

Search recent headlines + summaries by keyword, newest first. Use for "news about X", "what happened with X this week".

    Matching is case- and accent-insensitive substring search on the ORIGINAL-language text, so a
    Spanish word will not find German or Japanese items. Words separated by spaces must ALL appear;
    separate alternatives with "|". To search across languages give the key name/term in each
    language, e.g. "Noboa | ノボア" or "elecciones | Wahl | élection | election".
    Prefer short distinctive terms (names, places) over full sentences.

    Args:
        query: keywords; spaces = AND, "|" = OR between alternatives.
        days: look-back window in days (default 7, max ~14).
        lang: optional ISO 639-1 filter on the original language.
        n: max items (default 20, max 50).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNo
daysNo
langNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 only cover readOnly and openWorld, so the description carries the real behavioral load and does it well: substring matching semantics, case/accent insensitivity, per-language corpus limits, AND/OR operator behavior, and hard caps (days ~14, n 50). It stops short of describing result shape or what 'summary' fields contain.

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 and ordering, then matching rules, then per-arg notes. The cross-language examples are the most expensive part but they earn their place by teaching non-obvious query construction; a touch of redundancy in restating operators.

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 and thin annotations, the description supplies the matching model, language limitation, and parameter caps an agent needs to call it correctly. The only missing piece is any indication of what a returned item looks like, which matters for chaining into downstream tools.

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 coverage is 0%, so the description must do all the work, and it does: query documents space=AND and '|'=OR with worked bilingual examples, days documents default 7 and max ~14, lang documents ISO 639-1 original-language filtering, and n documents default 20 and max 50 — including max bounds absent from the schema.

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 (search), resource (recent headlines + summaries), and ordering (newest first), plus a keyword scope. It is clearly distinguishable from sources and compare_coverage, though it does not explicitly contrast itself with the sibling latest_news, which plausibly overlaps in 'recent news' territory.

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 concrete when-to-use phrasing ('news about X', 'what happened with X this week') that maps directly onto query construction. It lacks any explicit when-not/alternative-tool clause, which is the only gap at this tier.

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