FeedKeeper RSS/Atom reader and remote MCP Server

Get current curated newspaper edition

get_edition

Retrieve the current newspaper edition state, metadata, article list, and revision number so you can read the curated edition or pass its expected revision to publish it.

Instructions

Returns the authoritative edition state, publication metadata, article list, and revision number for the user's curated newspaper edition ('Deine Zeitung'). Returns the current revision (even if empty, expired, or dismissed), which must be passed as expectedRevision when calling publish_edition. Safe read-only.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.36.3Nov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and mostly succeeds: it declares the operation 'Safe read-only' and discloses the notable edge-case behavior that a revision is returned even when the edition is empty, expired, or dismissed. It does not address error conditions, whether an edition is lazily created, or the size/shape of the article list.

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 return contents and followed by the actionable revision hand-off. No filler, no restatement of the tool name.

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?

There is no output schema, so the description must describe returns — and it does, enumerating edition state, publication metadata, article list, and revision. The main residual gap is that the article list is mentioned without any hint of volume, ordering, or summarization depth.

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 there is no per-parameter meaning to add; baseline is 4. The mention of expectedRevision refers to a different tool's parameter and is correctly framed as a hand-off instruction rather than an input here.

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?

The description opens with a specific verb and resource: 'Returns the authoritative edition state, publication metadata, article list, and revision number for the user's curated newspaper edition.' It even names the concrete edition ('Deine Zeitung'), making it clearly distinguishable from siblings like get_overview or get_edition_candidates.

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?

It gives a concrete downstream instruction — the returned revision 'must be passed as expectedRevision when calling publish_edition' — which is exactly the kind of routing guidance an agent needs. It also clarifies that an empty/expired/dismissed edition still returns a revision, discouraging premature bail-out. It stops short of explicitly contrasting itself with get_edition_candidates or get_overview.

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