Skip to main content
Glama

zeit_headlines

Fetch DIE ZEIT main RSS top headlines ordered by recency; set a limit from 1 to 50 (default 10) to control how many articles are returned.

Instructions

Top headlines from DIE ZEIT (main RSS feed), 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": "zeit_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden; it discloses ordering ('newest first') and source feed but not freshness, error behavior, or an explicit read-only/no-side-effect statement. For a simple headline fetch this is adequate but not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the resource and ordering, then the limit rule. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has one parameter, and an output schema exists; the description covers source, ordering, and the limit constraint, so an agent can call it correctly. Sibling routing is the main remaining gap, but completeness for invocation is high.

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 description compensates fully for the only parameter by giving the valid range 1..50 and default 10. The schema only declares an integer with default 10, so the description adds real constraint meaning.

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?

The description states the exact resource (top headlines), source (DIE ZEIT main RSS feed), and ordering (newest first). It implicitly separates this from section-specific or search siblings via 'main RSS feed,' but never names an alternative, so sibling differentiation is not fully explicit.

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?

Use is implied for recent top headlines from the main feed, but there is no explicit when-to-use or when-not-to-use guidance. An agent must infer that section-specific or search tools are alternatives.

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