Skip to main content
Glama
danmarce

news-mcp

by danmarce
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

latest_news

Read-only

Fetch recent headlines newest first, filtered by source, language, country, category, or look-back window for news queries.

Instructions

Most recent headlines, newest first. Use for "what's the news", "latest from Ecuador", "what does DW say today", "tech news". All filters are optional and combine with AND.

    Args:
        source: feed id from `sources()` (e.g. "elcomercio", "bbc-mundo", "dw-de").
        lang: ISO 639-1 language of the original items (e.g. "es", "en", "de", "fr", "ar", "ja").
        country: ISO 3166 alpha-2 country of the outlet (e.g. "EC", "US", "DE"); "INT" = international.
        category: one of general, politics, economy, science, tech, sport.
        hours: look-back window in hours (default 24; up to ~336 = two weeks).
        n: max items (default 15, max 50).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNo
langNo
hoursNo
sourceNo
countryNo
categoryNo

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 already cover the read-only, non-open-world profile, and the description layers on genuinely useful behavior: filters combine with AND, defaults (24h/15 items), and caps (~336h, max 50). It does not describe result ordering beyond 'newest first' or pagination, but that is minor against the annotation coverage.

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 purpose followed by a clean per-argument list; every line adds information. Slightly long, but nothing is padding, so it stays efficient for a six-parameter tool.

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?

For a six-parameter, no-output-schema read tool, the description documents selection, filtering semantics, and limits thoroughly. Only the shape of returned items is unaddressed, which is acceptable given the read-only annotations.

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 carries the full burden and does so: every one of the six parameters gets meaning, format (ISO 639-1, ISO 3166 alpha-2), examples, defaults, and range for hours/n. This is exactly what a low-coverage schema requires.

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 resource and ordering ('Most recent headlines, newest first') plus its scope. It reads clearly as a general latest-news feed, distinguishable from news_by_topic, but it never names a sibling or explains the split between them.

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?

Concrete natural-language triggers ('what's the news', 'latest from Ecuador', 'what does DW say today', 'tech news') give an agent a clear sense of when to reach for it, and it points at sources() for feed ids. It lacks any when-not or explicit alternative-selection rules.

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