Skip to main content
Glama
freshrss-mcp

freshrss-mcp

by hrsather

freshrss_star

Idempotent

Marks up to 100 FreshRSS articles as starred using their IDs, so you can flag items for later review.

Instructions

Star articles by id (at most 100).

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": {
      "ids": "<ids>"
    },
    "name": "freshrss_star"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The description adds critical behavioral context by enforcing a maximum limit of 100 IDs. This is an operational constraint not present in the schema or annotations, which is valuable information for the AI agent.

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?

The definition is extremely concise, front-loading the core action and succinctly appending the necessary constraint in a single, clean sentence.

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?

For a simple, single-parameter tool, this definition provides all necessary operational information. The 'at most 100' constraint ensures the agent does not attempt to overwhelm the API.

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

Parameters3/5

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

Since schema description coverage is 0%, the description relies on the schema for parameter detail. The phrase 'by id' clarifies the nature of the input but does not add complex semantic meaning beyond the basic schema definition.

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 tool clearly states its action ('Star articles') and the resource being acted upon ('articles'). Although it is specific, it could benefit from explicitly distinguishing it from the inverse operation ('unstar') which is present in the sibling list.

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?

The description clearly dictates the input requirement (use 'id'), which is a form of usage guidance. However, it does not guide the user on when to use this specific function versus similar listing or retrieval functions.

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