Skip to main content
Glama
freshrss-mcp

freshrss-mcp

by hrsather

freshrss_export_opml

Read-onlyIdempotent

Export all FreshRSS subscriptions as an OPML file for backup or migration to another feed reader.

Instructions

Export all subscriptions as OPML.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description contributes only the scope detail that it exports all subscriptions with no filtering; it says nothing about size, rate limits, or whether the OPML is returned inline or as a file.

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?

One short sentence with zero filler, front-loading the action and the format. Nothing is wasted and nothing needs to be cut.

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?

An output schema exists, so return-value explanation is unnecessary, and annotations cover the safety profile; for a zero-parameter read tool this is nearly complete. The only residual gap is whether the caller receives an OPML document or a file path, which matters for chaining into the import tool.

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 nothing to disambiguate and no risk of misuse at the argument level. The description correctly signals the no-argument, all-subscriptions scope rather than implying any filters.

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 ("Export all subscriptions") plus the output format (OPML), so the agent knows exactly what it produces. It doesn't explicitly contrast with the inverse sibling freshrss_import_opml, but the direction is unambiguous from the verb.

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 only implied: agents can infer this is the tool for backup/migration or moving subscriptions to another reader. There is no explicit when/when-not statement and no named alternative, though the sibling set makes the counterpart obvious.

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