Skip to main content
Glama
tagesschau-mcp

tagesschau-mcp

tagesschau_headlines

Fetches top headlines from tagesschau.de, newest first, letting you set a result limit from 1 to 50 (default 10).

Instructions

Top headlines from tagesschau.de (alle Meldungen), newest first. limit: 1..50 (default 10).

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": "tagesschau_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden; it does disclose the source and that results are ordered newest-first, which is useful behavior. It does not state read-only nature, freshness/caching, rate limits, or total result count, and an output schema is supplied so return shape need not be covered.

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?

Two compact sentences that front-load the resource and scope, then the parameter constraint. No filler, though the parenthetical '(alle Meldungen)' is slightly cryptic to non-German readers.

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 one-parameter fetch tool with an output schema, the essentials are covered: what it returns, ordering, and parameter bounds. The main missing piece is explicit routing guidance relative to the section/search siblings.

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% and the schema only supplies a default of 10, so the description fully compensates by stating the valid range 1..50 and reaffirming the default. The single parameter's meaning and bounds are unambiguous.

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?

Names a specific resource and verb ('Top headlines from tagesschau.de'), plus scope ('alle Meldungen' = all news, not a section) and ordering ('newest first'). This implicitly separates it from section/regional/search siblings, though no alternative is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: 'alle Meldungen' suggests using this for unfiltered top news rather than section- or search-specific tools. There is no stated condition for preferring it over tagesschau_news_by_section or tagesschau_search_news.

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