FeedKeeper RSS/Atom reader and remote MCP Server

Get candidate articles for newspaper curation

get_edition_candidates

Selects a bounded shortlist of unread articles from the past 7 days, scored for editorial curation and user preferences, to prepare a newspaper edition with publish_edition.

Instructions

Use this tool ONLY when preparing to curate a newspaper edition with publish_edition. Returns a bounded shortlist of unread articles from the last 7 days scored for editorial curation, user reading preferences, and current revision. Do NOT use for general reading or browsing (use get_digest or get_new_items instead).

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_candidates"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of candidate articles to evaluate (1 to 200, default: 100)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.36.4Nov 9, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Maximum number of candidate articles to evaluate (1 to 200, default: 100)"
```
First observedv0.36.3Nov 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description still discloses key behavior: the result is a bounded shortlist of unread articles from the last 7 days, scored by editorial relevance, user preferences, and revision. It does not cover edge cases such as empty results or ordering, but it gives a strong behavioral picture for a read-only selection tool.

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?

The description is short, front-loaded, and structured around purpose, when-to-use, and when-not-to-use. Every sentence contributes to correct tool selection.

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?

For a single-parameter tool with no annotations and no output schema, the description supplies the critical context: eligibility scope, time window, scoring rationale, and downstream pairing with publish_edition. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the limit parameter is already fully documented in the schema. The description adds no extra meaning beyond saying the result is bounded, which is consistent with the schema but not additional parameter guidance.

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 uses a specific verb and resource: it returns a bounded shortlist of unread articles for edition curation. It clearly distinguishes this tool from general reading/browsing tools and names the downstream action, publish_edition.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance ('ONLY when preparing to curate a newspaper edition with publish_edition') and explicit when-not-to-use guidance with named alternatives ('use get_digest or get_new_items instead').

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