Skip to main content
Glama
spiegel-mcp

spiegel-mcp

spiegel_news_by_section

Fetches the newest headlines from a chosen SPIEGEL section, newest first, with a configurable limit of 1 to 50 items, so you can browse news by topic such as politics, sports, or science.

Instructions

Newest news of one SPIEGEL section, newest first. section: "politik", "ausland", "wirtschaft", "panorama", "sport", "kultur", "netzwelt", "wissenschaft", "geschichte", "gesundheit", "karriere", "mobilitaet" or "stil" (German names work too, e.g. "Mobilität"). limit: 1..50 (default 10).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "spiegel_news_by_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sectionYes

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 full burden, and it does disclose result ordering (newest first) and the limit default of 10 — genuinely behavioral facts. It does not say how invalid section names are handled, whether the limit caps total retrievable items, or anything about pagination, which matters for a listing tool.

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?

The purpose and ordering come first, then the two parameter facts, which is the right front-loading. The long slug list is bulky but every token earns its place given there is no enum in the schema.

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?

An output schema exists, so return-shape explanation is not required, and both parameters are fully specified in prose. The remaining gaps are edge-case behavior — invalid section handling and behavior at the 50-item ceiling — which are minor for a simple two-parameter listing tool.

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 description coverage is 0% — the schema shows only bare "string" and "integer" titles — so the description must carry everything, and it does: it enumerates all valid section slugs, notes that German names including umlauts ("Mobilität") work, and gives the limit range 1..50 with its default. Without this text the parameters would be uncallable.

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?

"Newest news of one SPIEGEL section, newest first" gives a specific resource (section news) and ordering (newest first), which separates it from article-fetching siblings. It stops short of naming a sibling or stating scope boundaries versus something like spiegel_headlines, so it is clear but not fully differentiated.

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 implied by the section-enumeration: this is the tool for browsing a single desk's latest items. There is no explicit when-to-use framing and no exclusion against the closely overlapping headlines sibling, leaving the agent to infer the boundary.

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