Skip to main content
Glama

zeit_sections

List DIE ZEIT sections with their slugs, German names, and RSS feed URLs so agents can choose valid feeds and avoid unavailable or redirected sections.

Instructions

The 10 DIE ZEIT sections with RSS feeds: slug, German name and feed URL. (kultur, wissen, geschichte and karriere have no RSS feed; ausland/deutschland/leben redirect to bot-walled pages.)

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": "zeit_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does add real context: four sections (kultur, wissen, geschichte, karriere) have no RSS feed, and ausland/deutschland/leben redirect to bot-walled pages. That is exactly the kind of caveat that prevents downstream failures. It stops short of saying whether the list is static or fetched live and whether the call can fail.

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?

One front-loaded sentence plus a single parenthetical of exclusions, with zero filler. The most decision-relevant information (what is returned) leads, and the caveats follow compactly.

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 values need not be explained, and for a zero-argument metadata tool the description covers purpose and key caveats adequately. The only minor gap is not stating whether the section list is a fixed constant or retrieved live, which matters for caching and failure expectations.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter meaning for the description to add or omit.

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 first clause names the resource precisely ('The 10 DIE ZEIT sections') and enumerates the returned fields (slug, German name, feed URL), so an agent knows exactly what it gets. It does not explicitly contrast itself with siblings like zeit_news_by_section or zeit_headlines, leaving the reference-vs-search distinction to inference.

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 a lookup used to discover section slugs before calling a section-scoped tool, and the caveats about which sections lack feeds steer selection. There is no explicit 'use this when...' or 'do not use for...' statement naming an alternative.

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