Skip to main content
Glama
freshrss-mcp

freshrss-mcp

by hrsather

freshrss_search_articles

Read-onlyIdempotent

Searches FreshRSS article titles and bodies case-insensitively when no server-side search is available, scanning recent articles and reporting if older items were skipped.

Instructions

Case-insensitive text search over title and body. FreshRSS has no server-side search, so this scans the newest max_scan articles (at most 500) of the stream; the result reports scanned and truncated (true when older articles were not checked).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
streamNoall
targetNo
max_scanNo
max_charsNo
unread_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the key architectural constraint: FreshRSS has no server-side search, so results come from scanning only the newest max_scan articles capped at 500. It also explains that the response reports 'scanned' and 'truncated', telling the agent when results may be incomplete — exactly the kind of caveat that prevents false negatives.

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 sentences, both dense with decision-relevant information, front-loaded with what the tool does before the mechanism caveat. No filler or restatement of the name.

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?

An output schema exists and the description wisely flags the 'scanned'/'truncated' fields, and the read-only nature is covered by annotations. What is missing is any explanation of the scope parameters (stream, target, unread_only) that determine which articles are even eligible for scanning, leaving the agent unable to reason about coverage.

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 7 parameters, so the description must carry the load, but it only explains max_scan (and its 500 ceiling). The meaning of 'stream', 'target', 'limit', 'max_chars', and 'unread_only' is left entirely undefined, which is a significant gap for a search tool where scope parameters change results.

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?

Names a specific verb and resource ('text search over title and body') and states the case-insensitivity scope, which is clearly distinct from listing or fetching an article. It does not explicitly name a sibling like freshrss_list_articles as the alternative, so differentiation is implied rather than stated.

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 implied by describing the scan mechanism, so an agent can infer this is the tool for keyword lookup. However, there is no explicit statement of when to prefer this over freshrss_list_articles or freshrss_get_article, and no guidance on choosing between the two when browsing versus searching.

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