Skip to main content
Glama
tono628develop

feed-reader-mcp

by tono628develop
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v0.1.0

  • Disambiguation5/5

    The two tools have clearly distinct purposes: fetch_feed retrieves a single feed, while fetch_many fetches multiple feeds and merges them. There is no ambiguity about which tool to use based on the input.

    Naming Consistency5/5

    Both tools follow the verb_noun pattern with 'fetch' as the verb. While 'many' is not a traditional noun, the prefix 'fetch_' is consistent and the second part clearly indicates the number of feeds, making the naming predictable.

    Tool Count3/5

    With only two tools, the server feels minimal. For a feed reader, one might expect additional operations like adding, listing, or removing feeds, but as a simple fetching utility, the count is borderline acceptable.

    Completeness4/5

    The tools cover the core functionality of fetching a single feed and fetching multiple feeds for a digest. Minor gaps include no ability to fetch feed metadata or manage subscriptions, but for the stated purpose of parsing and returning items, it is largely complete.

  • Average 4/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 3 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior3/5

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

    No annotations are present, so the description carries the full burden. It states the core behavior (fetch, parse, return items) and even lists fields, but does not disclose edge cases, error handling, authentication, or response format. This is adequate but minimal, offering no extra depth.

    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, front-loaded sentence that states the action and output without redundancy. Every element is meaningful and the length is ideal for a tool of this simplicity.

    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?

    The tool is simple and the schema is self-explanatory. The description lists the return fields, which is helpful since there is no output schema. However, it does not mention the effect of the 'limit' parameter on the response or compare with 'fetch_many', leaving minor gaps.

    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 schema covers both parameters fully: 'url' with format uri and 'limit' with default, minimum, and maximum. The description adds no additional parameter details, but since schema coverage is 100%, the baseline score of 3 is appropriate.

    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 clearly states the tool fetches and parses a single RSS or Atom feed and returns recent items with specific fields (title, link, date, snippet). The word 'single' distinguishes it from the sibling tool 'fetch_many', making the purpose explicit and non-confusable.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines4/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    The description provides clear context that this tool is for a single feed, which implies it is the right choice when one feed is needed. It does not explicitly name the alternative 'fetch_many' or provide exclusion criteria, but the 'single' qualifier gives sufficient guidance for most cases.

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

  • Behavior3/5

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

    No annotations are provided, so the description must disclose behavior. It mentions the merged, date-sorted output but does not cover failure modes, network errors, or partial feed handling. This is minimal but not entirely bare.

    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?

    Two sentences with the main action front-loaded and no redundant phrasing. Each sentence carries useful information.

    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?

    The tool has a low complexity (2 params) and the schema fully documents parameters. The description explains the returned data (merged, date-sorted list) but does not specify item structure, which would be helpful given no output schema. Still, it is adequate for tool selection.

    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 schema covers 100% of parameters with descriptions ('List of feed URLs', 'Maximum items to take from each feed'), so the baseline is 3. The description adds no extra parameter detail beyond what the schema provides.

    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 clearly states the tool fetches multiple RSS/Atom feeds and returns a merged, date-sorted list, distinguishing it from the sibling tool fetch_feed for single feeds. The verb 'Fetch' and resource 'feeds' are specific.

    Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

    Usage Guidelines4/5

    Does the description explain when to use this tool, when not to, or what alternatives exist?

    The description provides context for use ('Useful for building a digest') and implies it is for multiple feeds by using 'several'. However, it does not explicitly contrast with fetch_feed or state when not to use it.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

feed-reader-mcp MCP server

Copy to your README.md:

Score Badge

feed-reader-mcp MCP server

Copy to your README.md:

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/tono628develop/feed-reader-mcp'

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