Skip to main content
Glama

list_favicons

Retrieve favicons for subscribed RSS feeds using the Fever API to visually identify feed sources in your FreshRSS instance.

Instructions

List favicons for subscribed feeds (Fever API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration and handler implementation for list_favicons in fever-handlers.ts.
    server.registerTool(
      'list_favicons',
      {
        description: 'List favicons for subscribed feeds (Fever API)',
        inputSchema: listFaviconsSchema,
      },
      wrapTool('list_favicons', async () => {
        const favicons = await client.fever.listFavicons();
        if (favicons.length === 0) {
          return textResult('No favicons found.');
        }
        const text = favicons
          .map((f) => `- Feed ${f.feedId.toString()}: favicon available`)
          .join('\n');
        return textResult(text);
      })
    );
  • Schema definition for the list_favicons tool.
    export const listFaviconsSchema = z.object({}).strict();
  • The underlying API call that fetches the favicon data.
    async listFavicons(): Promise<Favicon[]> {
      const data = await this.http.postFever<FeverFaviconsResponse>({ favicons: '1' });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to specify the return format (URLs, base64 data, binary blobs), pagination behavior, or authentication requirements. While 'List' implies read-only, the description does not confirm idempotency or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description consists of a single, front-loaded sentence with no redundant words or filler. It immediately communicates the core operation. However, given the lack of output schema and annotations, the extreme brevity borders on under-specification rather than optimal conciseness.

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?

While adequate for a zero-parameter tool, the description fails to compensate for the missing output schema by describing the returned data structure. It also omits the relationship to `get_feed_favicon`, which is critical context given the sibling tool names suggest overlapping functionality.

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 input schema contains zero parameters, establishing a baseline score of 4. The description does not need to elaborate on parameter semantics, though it correctly implies no filtering arguments are accepted (listing all subscribed feeds).

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 description uses the specific verb 'List' with resource 'favicons' and scope 'subscribed feeds', clearly stating the tool's function. The 'Fever API' parenthetical adds protocol context. However, it lacks explicit differentiation from the sibling tool `get_feed_favicon`, which appears to perform a similar operation for individual feeds.

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 provides no guidance on when to use this bulk listing tool versus the singular `get_feed_favicon`, nor does it mention prerequisites, rate limits, or caching behavior. The agent receives no signals about optimal invocation patterns.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alysson-souza/freshrss-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server