Skip to main content
Glama
VectorInstitute

MCP Goodnews

fetch_list_of_goodnews

Retrieve positive news headlines filtered by category, using sentiment analysis to identify uplifting stories from NewsAPI.

Instructions

Fetch a list of headlines and return only top-ranked news based on positivity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoall

Implementation Reference

  • The `fetch_list_of_goodnews` tool handler which fetches headlines based on categories and then uses `GoodnewsRanker` to filter for positive news.
    @mcp.tool()
    async def fetch_list_of_goodnews(
        category: Literal["all", "science", "health", "technology"] = "all",
    ) -> str:
        """Fetch a list of headlines and return only top-ranked news based on positivity."""
    
        # make request to top-headlines newsapi
        articles = []
        if category == "all":
            categories = ["science", "health", "technology"]
        else:
            categories = [category]
        for cat in categories:
            top_articles = await get_top_headlines(cat)
            articles.extend(top_articles)
    
        # rank the retrieved handlines and get only most positive articles
        ranker = GoodnewsRanker(model_name="command-a-03-2025")
        goodnews = await ranker.rank_articles(articles)
    
        return goodnews  # type: ignore[no-any-return]
  • Tool registration using the `@mcp.tool()` decorator in the `FastMCP` server instance.
    @mcp.tool()
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions filtering by positivity but lacks details on permissions, rate limits, data freshness, or what 'top-ranked' entails (e.g., algorithm, recency). This leaves significant gaps for a tool that likely involves external data fetching.

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 is a single, efficient sentence that gets straight to the point without unnecessary words. It's appropriately sized for a simple tool, though it could be slightly more informative without losing conciseness.

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 no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain return values, error handling, or behavioral traits like how 'positivity' is measured, making it inadequate for effective tool use.

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?

Schema description coverage is 0%, so the description must compensate. It doesn't mention the 'category' parameter at all, failing to add meaning beyond the schema. However, with only one parameter and an enum in the schema, the baseline is moderate, but the description offers no parameter context.

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 ('fetch a list of headlines') and the resource ('top-ranked news based on positivity'), making the purpose understandable. However, it doesn't differentiate from siblings since there are none, and 'top-ranked' could be more specific about ranking criteria.

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or contextual triggers. The description implies filtering by positivity but doesn't specify scenarios or limitations for usage.

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/VectorInstitute/mcp-goodnews'

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