Skip to main content
Glama
narumiruna

coindesk-mcp

read_news

Extract structured news content from CoinDesk articles, including title, author, publication date, and full text, using a provided URL. Simplifies article retrieval and parsing for quick insights.

Instructions

Retrieves and extracts the full content of a specific news article from CoinDesk.

Fetches the HTML content from the provided URL, processes it to extract
structured news information including title, subtitle, author, publication date,
and article content.

Args:
    url (str): The complete URL of the CoinDesk news article to retrieve

Returns:
    str: A formatted string containing the article's title, subtitle, author,
         publication information, and content preview

Raises:
    HTTPStatusError: If the URL request fails
    Exception: If article parsing encounters errors

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Implementation Reference

  • The read_news tool handler: decorated with @mcp.tool() for registration, fetches article HTML using the helper function, converts it to Markdown using markdownify, and returns the Markdown content.
    @mcp.tool()
    async def read_news(url: str) -> str:
        """
        Fetches article HTML from URL and converts it to Markdown.
    
        Args:
            url: Article URL to retrieve
    
        Returns:
            Markdown-formatted article content
        """
        html = await fetch_text_from_url(url)
        markdown = md(html, strip=["a", "img"])
        return markdown
  • Supporting utility function fetch_text_from_url used by read_news to asynchronously retrieve HTML content from the provided URL using httpx.
    async def fetch_text_from_url(url: str) -> str:
        """
        Asynchronously retrieves text content from a specified URL.
    
        Makes an HTTP GET request to the provided URL and returns the response
        content as text. Handles connection setup and cleanup automatically.
    
        Args:
            url (str): The URL to fetch content from
    
        Returns:
            str: The text content received from the URL
    
        Raises:
            HTTPStatusError: If the HTTP request returns a non-2xx status code
            RequestError: If a network-related error occurs during the request
        """
        async with httpx.AsyncClient() as client:
            response = await client.get(url)
            response.raise_for_status()
            return response.text
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behaviors: it fetches HTML content, processes it for structured extraction, and mentions potential error conditions (HTTPStatusError, parsing errors). It doesn't cover rate limits, caching behavior, or authentication requirements, but provides solid operational context.

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 well-structured with clear sections (purpose, args, returns, raises) and front-loaded key information. Some sentences could be more concise (e.g., 'Fetches the HTML content from the provided URL, processes it to extract structured news information' could be tightened), but overall it's efficient and organized.

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?

For a single-parameter tool with no annotations and no output schema, the description provides good completeness: clear purpose, parameter explanation, return format description, and error conditions. It could benefit from more explicit sibling tool differentiation and operational constraints, but covers the essential context well.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage and only one parameter, the description fully compensates by clearly explaining the 'url' parameter's purpose ('complete URL of the CoinDesk news article to retrieve') and constraints. It adds essential meaning beyond the bare schema.

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 specific action ('retrieves and extracts full content'), resource ('news article from CoinDesk'), and scope ('structured news information including title, subtitle, author, publication date, and article content'). It distinguishes from the sibling tool 'recent_news' by focusing on individual article extraction rather than recent news listing.

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

Usage Guidelines3/5

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

The description implies usage context through the mention of 'CoinDesk news article' and the required URL parameter, but doesn't explicitly state when to use this tool versus the 'recent_news' sibling. No explicit guidance on prerequisites, alternatives, or exclusion criteria is provided.

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

Related 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/narumiruna/coindesk-mcp'

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