Skip to main content
Glama
JeremyLakeyJr

Friday MCP Server

get_world_news

Retrieve a multi-source snapshot of world headlines. Obtain a broad view of global news from multiple sources.

Instructions

Fetch a multi-source snapshot of world headlines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'get_world_news' tool handler: fetches world headlines concurrently from BBC, NYT, and Al Jazeera RSS feeds, returning a flat list of dicts with source, title, summary, and link.
    @mcp.tool()
    async def get_world_news() -> list[dict[str, str]]:
        """Fetch a multi-source snapshot of world headlines."""
        async with httpx.AsyncClient(follow_redirects=True, timeout=15.0) as client:
            results = await asyncio.gather(*[_fetch_feed(client, url) for url in SEED_FEEDS])
        return [item for group in results for item in group]
  • SEED_FEEDS list defining the RSS sources (BBC World, NYT World, Al Jazeera) that 'get_world_news' fetches from.
    SEED_FEEDS = [
        "https://feeds.bbci.co.uk/news/world/rss.xml",
        "https://rss.nytimes.com/services/xml/rss/nyt/World.xml",
        "https://www.aljazeera.com/xml/rss/all.xml",
    ]
  • Helper function '_fetch_feed' that parses an RSS feed XML, extracts up to 4 items with title, summary (HTML stripped), link, and source domain.
    async def _fetch_feed(client: httpx.AsyncClient, url: str) -> list[dict[str, str]]:
        response = await client.get(url, headers={"User-Agent": "Friday-MCP-Server/0.1"})
        response.raise_for_status()
    
        root = ET.fromstring(response.content)
        feed_items: list[dict[str, str]] = []
        for item in root.findall(".//item")[:4]:
            description = item.findtext("description") or ""
            feed_items.append(
                {
                    "source": url.split("/")[2],
                    "title": item.findtext("title") or "Untitled",
                    "summary": re.sub(r"<[^>]+>", "", description).strip(),
                    "link": item.findtext("link") or "",
                }
            )
        return feed_items
  • The 'register' function that registers all web tools (search_web, fetch_url, get_world_news) on the MCP server instance via @mcp.tool() decorators.
    def register(mcp, *, config) -> None:
        @mcp.tool()
        async def search_web(query: str, max_results: int = 5) -> list[dict[str, str]]:
            """Search the web with DuckDuckGo and return the top results."""
    
            def _search() -> list[dict[str, str]]:
                from duckduckgo_search import DDGS
    
                with DDGS() as ddgs:
                    return [
                        {
                            "title": result.get("title", ""),
                            "snippet": result.get("body", ""),
                            "url": result.get("href", ""),
                        }
                        for result in ddgs.text(query, max_results=max_results)
                    ]
    
            return await asyncio.to_thread(_search)
    
        @mcp.tool()
        async def fetch_url(url: str) -> str:
            """Fetch the raw text of a URL, truncated to the configured limit."""
            async with httpx.AsyncClient(follow_redirects=True, timeout=15.0) as client:
                response = await client.get(url)
                response.raise_for_status()
                return response.text[: config.max_fetch_chars]
    
        @mcp.tool()
        async def get_world_news() -> list[dict[str, str]]:
            """Fetch a multi-source snapshot of world headlines."""
            async with httpx.AsyncClient(follow_redirects=True, timeout=15.0) as client:
                results = await asyncio.gather(*[_fetch_feed(client, url) for url in SEED_FEEDS])
            return [item for group in results for item in group]
  • Tool registry module that calls 'web.register(mcp, config=config)' to register the web tools (including get_world_news) on the MCP server.
    def register_all_tools(mcp, *, config, skill_store) -> None:
        system.register(mcp, config=config)
        utils.register(mcp)
        web.register(mcp, config=config)
        workspace.register(mcp, config=config)
        skills.register(mcp, skill_store=skill_store)
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only mentions 'multi-source snapshot' without details on source count, freshness, ordering, or output structure. The tool appears to be a simple fetch, but lacks transparency on aggregation behavior.

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 with no wasted words. It is concise and immediately clear.

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?

Given the zero-parameter simplicity and presence of an output schema, the description is nearly complete. It could optionally mention the output nature, but the rule states output schema fills that role. Adequate for a straightforward tool.

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 zero parameters and schema coverage is 100%. The description is vacuously sufficient for parameters, earning a baseline score of 4 as per rubric for zero-parameter tools.

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 'Fetch a multi-source snapshot of world headlines' clearly states the action (fetch) and the resource (world headlines), and implies aggregation from multiple sources, distinguishing it from sibling tools like search_web or fetch_url.

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 over alternatives, nor any exclusions or prerequisites. It is a single-purpose statement without contextual usage advice.

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/JeremyLakeyJr/mcp-server'

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