Skip to main content
Glama

get_feed_favicon

Retrieve favicon images for RSS feeds in FreshRSS to visually identify and organize your subscriptions.

Instructions

Get a feed favicon as an MCP resource (Fever API)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedIdYesFeed ID to get favicon for

Implementation Reference

  • The handler implementation for the 'get_feed_favicon' tool, which fetches and returns a feed's favicon.
    wrapTool('get_feed_favicon', async (args: z.infer<typeof getFaviconSchema>) => {
      const favicons = await client.fever.listFavicons();
      const feedIdNum = Number(args.feedId);
      const found = favicons.find((f) => f.feedId === feedIdNum);
      if (found === undefined) {
        return textResult(`No favicon for feed ${args.feedId}.`);
      }
      const parsed = parseDataUri(found.dataUri);
      if (parsed === null) {
        return textResult('Invalid favicon data.');
      }
      return resourceResult({
        uri: `freshrss://favicon/${args.feedId}`,
        blob: parsed.base64,
        mimeType: parsed.mimeType,
      });
    })
  • Registration of the 'get_feed_favicon' tool with the MCP server.
    server.registerTool(
      'get_feed_favicon',
      {
        description: 'Get a feed favicon as an MCP resource (Fever API)',
        inputSchema: getFaviconSchema,
      },
  • Zod schema definition for the 'get_feed_favicon' tool inputs.
    export const getFaviconSchema = z
      .object({
        feedId: z.string().describe('Feed ID to get favicon for'),
      })
      .strict();
Behavior3/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. It clarifies the return format (MCP resource) and references the Fever API context, but omits error handling (e.g., missing favicons), caching behavior, or whether this is a read-only operation.

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 single-sentence description is efficiently structured and front-loaded with the core action. However, the parenthetical '(Fever API)' adds domain context that may be opaque without external knowledge, slightly reducing clarity-per-word efficiency.

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?

Given the tool's simplicity (single parameter) and lack of output schema, the description adequately covers the basic operation but lacks completeness regarding error states, return value structure, or Fever API specific behaviors.

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?

The input schema has 100% description coverage for the feedId parameter. The description does not add additional semantic meaning, syntax examples, or validation rules beyond what the schema already provides, warranting the baseline score.

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 a specific verb ('Get') and resource ('feed favicon') and clarifies the output format ('as an MCP resource'). While it implies singularity (distinguishing from list_favicons), it does not explicitly differentiate when to use this versus the sibling list_favicons tool.

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 tool versus alternatives like list_favicons, nor does it mention prerequisites such as needing a valid feedId from list_feeds first.

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