Skip to main content
Glama
spiegel-mcp

spiegel-mcp

spiegel_search_news

Find news articles on spiegel.de by keyword across headline and section feeds; results are de-duplicated and sorted newest first with a configurable limit.

Instructions

Search spiegel.de news by keyword (title + description). query: free text, e.g. "Ronaldo" or "Bundestag". limit: 1..50 (default 10). Searches the headlines feed plus all 13 section feeds client-side (the site search page needs a session/consent flow), newest first, de-duplicated by link.

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": {
      "query": "<query>"
    },
    "name": "spiegel_search_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

With no annotations, the description carries the full burden and does real work: it discloses that the search is done client-side across 14 feeds and explains the reason (the site search page needs a session/consent flow), plus ordering (newest first) and de-duplication by link. It stops short of noting that client-side feed scanning limits coverage to recent items or any request-cost implications.

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 with the purpose, then parameter semantics, then implementation rationale. Dense and mostly waste-free, though the parenthetical about the session/consent flow is a justification detail that could be trimmed in a tighter definition.

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-value explanation is unnecessary. For a two-parameter search tool the description covers purpose, ordering, de-duplication, and coverage source; the only meaningful omission is that client-side feed scanning means results are bounded by what those feeds contain, not the full archive.

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%, so the description must define both parameters and it does: query is free text with concrete examples, and limit is constrained to 1..50 with a stated default of 10. No parameter meaning is left ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Search spiegel.de news by keyword") and pins down the match scope as title + description. The note that it scans the headlines feed plus all 13 section feeds distinguishes it from per-section siblings like spiegel_news_by_section and spiegel_headlines without needing to open their schemas.

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 context is implied by the keyword-search framing and the example queries ("Ronaldo", "Bundestag") and by the explanation of why the site search page is bypassed. However, it never explicitly states when to prefer this over spiegel_headlines or spiegel_news_by_section, nor any when-not condition, so the agent must infer routing.

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