Skip to main content
Glama

get rss feed

Retrieve RSS feeds from TabNews to access content updates and notifications directly within AI tools.

Instructions

To get the rss feed from tabnews

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool definition including the handler function for "get rss feed", which fetches the RSS feed using the service and returns it formatted as MCP text content.
    export const getRssFeedTool = {
      name: "get rss feed",
      description: "To get the rss feed from tabnews",
      parameters: {},
      handler: async (): Promise<McpResponse> => {
        try {
          const result = await getRssFeed();
    
          const content: McpTextContent = {
            type: "text",
            text: `RSS Feed:\n\n${result}`,
          };
    
          return {
            content: [content],
          };
        } catch (error) {
          if (error instanceof Error) {
            throw new Error(`Failed to get rss feed: ${error.message}`);
          } else {
            throw new Error("Failed to get rss feed");
          }
        }
      },
    };
  • src/index.ts:80-85 (registration)
    Registration of the "get rss feed" tool in the MCP server by calling server.tool with its name, description, parameters, and handler.
    server.tool(
      getRssFeedTool.name,
      getRssFeedTool.description,
      getRssFeedTool.parameters,
      getRssFeedTool.handler
    );
  • Supporting utility function that fetches the raw RSS feed content from the TabNews API endpoint.
    export async function getRssFeed(): Promise<string> {
      const response = await fetch(`${TABNEWS_API_URL}/contents/rss`);
      const data = await response.text();
    
      return data;
    }
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. It only states what the tool does ('get the rss feed'), but doesn't mention any behavioral traits like whether it's read-only, requires authentication, has rate limits, or what the output format might be. This leaves significant gaps in understanding how the tool behaves.

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 description is a single, straightforward sentence that directly states the tool's purpose without any unnecessary words. It's front-loaded and efficiently communicates the core function, making it highly concise and well-structured for its simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete for a tool that retrieves data. It doesn't explain what the RSS feed contains, how it's structured, or any limitations (e.g., update frequency, data scope). For a data retrieval tool with no structured context, more detail is needed to be fully helpful.

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 has 0 parameters, and the schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for this scenario is 4, as the description doesn't need to compensate for any parameter documentation gaps, and it appropriately avoids redundant information.

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 clearly states the action ('get') and resource ('rss feed from tabnews'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get content' or 'get contents', which might retrieve similar data but in different formats or scopes, so it's not fully specific about what makes this tool unique.

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, such as sibling tools like 'get content' or 'get contents'. It lacks context about scenarios where an RSS feed is preferred over other data retrieval methods, leaving the agent without usage direction.

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/renant/mcp-tabnews'

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