Skip to main content
Glama
spiegel-mcp

spiegel-mcp

spiegel_latest_videos

Fetches SPIEGEL TV and video reports in reverse chronological order, letting you set a result limit from 1 to 50.

Instructions

Latest SPIEGEL videos (SPIEGEL TV and video reports), 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_latest_videos"
  }
}

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 present, the description carries the full burden, and it does disclose meaningful traits: results are ordered newest-first and the limit is bounded 1..50 with a default of 10. It does not say whether results are paginated, cached, or live, and gives no indication of rate limits or freshness window beyond 'latest'.

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 compact sentences, front-loaded with the resource and ordering before the constraint detail. 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 single-parameter read tool with an output schema handling return values, the description covers purpose, ordering, and the only parameter's constraints. Only minor gaps remain, such as freshness of 'latest' and whether more results can be fetched beyond 50.

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 declares a default of 10 with no bounds or meaning. The description compensates by specifying the valid range (1..50), the default (10), and that it controls result count, which is more than the schema provides.

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 gives a specific verb-and-resource pair ('Latest SPIEGEL videos'), clarifies the content type ('SPIEGEL TV and video reports'), and states ordering ('newest first'). It does not explicitly contrast itself with siblings like spiegel_headlines or spiegel_search_news, but the resource distinction is clear enough to separate it from article/news tools.

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 browsing recent video content rather than articles or search. There is no explicit when-to-use vs when-not guidance and no named alternative for, e.g., finding a specific video by keyword.

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