Skip to main content
Glama
spiegel-mcp

spiegel-mcp

spiegel_get_article

Fetch a spiegel.de article by URL to retrieve its headline, summary, date, author, and body text; paywalled pieces are flagged with only the free teaser returned.

Instructions

Text of one spiegel.de article: headline, description, publish date, author and the article body. url: a spiegel.de article link, e.g. from spiegel_headlines. Free articles return the full body; SPIEGEL+ (paywalled) articles return paywalled: true with only the freely available summary/teaser — the full text stays behind the paywall and is never fabricated.

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": {
      "url": "<url>"
    },
    "name": "spiegel_get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden, and it delivers the most important behavioral fact: paywalled SPIEGEL+ articles return paywalled: true with only the free teaser, and the full text is never fabricated. That is exactly the kind of outcome an agent needs to plan around. It stops short of describing failure handling for invalid URLs, rate limits, or auth needs, which keeps it off a 5.

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?

Three sentences, front-loaded with what is returned, then the parameter, then the paywall caveat. Every sentence earns its place. Minor redundancy in restating the paywall boundary twice ('only the freely available summary/teaser' and 'the full text stays behind the paywall').

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?

An output schema exists, so return values need no further explanation, and the description still summarizes the payload helpfully. For a single-parameter fetch tool, the purpose, the input origin, and the paywall edge case are all covered — nothing an agent needs in order to call it correctly is missing.

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 description coverage is 0% — the schema only labels the field 'Url' — so the description must compensate, and it does by defining the parameter as a spiegel.de article link and pointing to spiegel_headlines as where such links come from. It adds no format or canonicalization detail beyond that example, so it is good but not exhaustive.

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 — retrieving the text of one spiegel.de article — and enumerates what comes back (headline, description, publish date, author, body). It also distinguishes itself from spiegel_headlines by naming it as the source of the url, so an agent can tell the two apart without opening a schema.

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

Usage Guidelines4/5

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

The description implies the correct usage pattern clearly: take a spiegel.de article link, e.g. one obtained from spiegel_headlines, and fetch that single article. It does not explicitly exclude alternatives or state when not to call it (e.g. for keyword discovery, where spiegel_search_news would be appropriate), so it falls short of full when/when-not guidance.

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