Skip to main content
Glama
spiegel-mcp

spiegel-mcp

spiegel_headlines

Fetch top headlines from spiegel.de in newest-first order and control the result count (1–50, default 10).

Instructions

Top headlines from spiegel.de (Schlagzeilen), 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": "spiegel_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose result ordering (newest first) and the size parameter bounds, which is useful. It says nothing about freshness/caching, rate limits, authentication, or behavior when fewer items than the limit exist, so the mutation-free read profile is only partially covered.

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 lines, front-loaded with what is returned and how it is ordered, then the one parameter constraint. No filler or redundancy.

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 simple one-parameter read tool with an output schema, the description covers purpose, ordering, and the parameter constraint. Only minor gaps remain (no statement about what happens when the feed has fewer items than the limit, or about result staleness).

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 0% and the single parameter's schema entry only shows a default of 10. The description compensates by supplying the valid range (1..50) and restating the default, which is exactly the missing semantic detail an agent needs to call it correctly.

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 names the specific resource and source (top headlines / Schlagzeilen from spiegel.de) and states the ordering (newest first), which is more precise than a bare name restatement. It does not explicitly distinguish itself from siblings such as spiegel_news_by_section or spiegel_search_news, so it stops short of a 5.

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: an agent can infer this is the tool for an unfiltered current-headlines listing, versus search or section browsing. There is no explicit when-to-use/when-not statement and no named alternative, leaving routing to inference from the sibling names.

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