Skip to main content
Glama
freshrss-mcp

freshrss-mcp

by hrsather

freshrss_get_article

Read-onlyIdempotent

Retrieve a FreshRSS article by its ID as plain text, limited by max_chars to control output size and indicate truncation.

Instructions

Get one article by its id, with plain text up to max_chars (see truncated).

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": {
      "id": "<id>"
    },
    "name": "freshrss_get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
max_charsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context. It does: content is returned as plain text, capped at max_chars, and may be truncated. It does not mention behavior for an unknown id, which is a modest gap.

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?

A single compact sentence with the resource, the key parameter, and the truncation caveat front-loaded. No filler or repetition of the tool 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, so return structure needn't be described, and annotations cover safety. What remains unaddressed is failure behavior for a missing or invalid id, which matters for a lookup tool an agent may call with guessed ids.

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?

Schema coverage is 0%, so the description must carry parameter meaning, and it largely does: it explains that max_chars caps the plain-text length and points at the `truncated` indicator. It says nothing about the id's format or source, leaving that parameter thin.

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?

States a specific verb and resource: 'Get one article by its id'. The 'one article' phrasing distinguishes it from list/search siblings well enough that an agent knows it is a single-item fetch, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this versus freshrss_list_articles or freshrss_search_articles, nor on prerequisites such as where an id comes from. 'By its id' only weakly implies the caller must already hold an id.

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