Skip to main content
Glama
rss-mcp

rss-mcp

by huangcheng

search_entries

Search cached RSS/Atom entries by full-text query across titles, summaries, and content; returns matching entries without bodies, so call read_entry for full article content.

Instructions

Full-text search over cached title, summary, and content. Omits entry bodies; use read_entry for full content.

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": {
      "query": "<query>"
    },
    "name": "search_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
unread_onlyNo
subscription_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden and does add two real behavioral facts: results are drawn from a cache and bodies are excluded. It says nothing about relevance ordering, pagination via limit, permission scope, or result size, which are the traits an agent would want for a search endpoint. The output schema covers the return shape, so omitting that is not penalized.

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 tightly written sentences with the core purpose front-loaded and the caveat plus escape hatch second. No filler and no redundancy with the structured fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema removes any need to explain return values, and the body-omission caveat is present, so the essentials are covered. However, for a four-parameter filtered search with no annotations and zero schema coverage, the absence of any filter or limit guidance leaves an agent guessing at invocation details.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters, so the description should compensate, and it largely does not. It clarifies that 'query' matches title, summary, and content, but says nothing about limit, unread_only, or subscription_id, leaving three parameters with no semantics anywhere.

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 names a specific verb and resource ('Full-text search over cached title, summary, and content') and delimits the searchable fields, which is enough for an agent to understand the operation. It explicitly separates itself from read_entry, though it does not contrast itself with list_entries, so it falls short of full sibling differentiation.

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 one explicit routing rule: results omit entry bodies, so use read_entry when full content is required. That is a genuine when-to-use alternative, but there is no guidance on when this beats list_entries or when the unread_only/subscription_id filters should be applied.

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