Skip to main content
Glama
Sign In
rss-news

rss-news

by max1ab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_subscriptions

Retrieve all subscribed RSS feeds with their sync status and metadata. Use to verify current subscriptions and check last update times.

Instructions

List subscribed RSS feeds and their current sync metadata.

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

Input Schema

NameRequiredDescriptionDefault
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. The verb 'List' transparently signals a read-only operation, and 'current sync metadata' indicates what state is returned. It does not disclose pagination or error behavior, but for a simple list tool the core behavior is clear.

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, front-loaded sentence conveys the tool's purpose and output without any filler. Every word adds information, making it easy for an agent to parse quickly.

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?

For a one-optional-parameter list tool with no output schema, the description is minimally adequate: it names the returned object types. However, it omits category filtering semantics and any details about how sync metadata is represented, leaving an agent to guess at the exact call behavior.

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% for the one optional 'category' parameter, and the description never mentions it or explains how it filters results. The parameter name is self-explanatory, but the description adds no meaning beyond the schema and fails to compensate for the missing schema documentation.

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 ('List') and resource ('subscribed RSS feeds') and adds 'current sync metadata', making its read-only listing purpose unmistakable. This clearly distinguishes it from mutation-focused siblings like upsert_subscriptions and remove_subscriptions.

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?

The description implies the tool is for viewing subscriptions, but it gives no explicit guidance on when to choose it over alternatives such as fetch_news or sync_news, and it does not mention any exclusions or sibling tools. An agent must infer the appropriate context from the verb alone.

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

Deploy Server

Other Tools