Skip to main content
Glama

get_latest

Get news articles published within the last 24 hours, optionally filtered by category, sorted with most recent first.

Instructions

Latest news from the last 24 hours. Optionally scoped to a category. Returns posts ordered newest-first. Use for 'what's new today?' or 'what happened in DeFi today?'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoen-US
categoryNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'get_latest'. Decorated with @mcp.tool, it accepts lang, category, and limit parameters, creates a ZippClient, and delegates to the client's get_latest method.
    @mcp.tool(
        name="get_latest",
        description=(
            "Latest news from the last 24 hours. Optionally scoped to a "
            "category. Returns posts ordered newest-first. Use for 'what's "
            "new today?' or 'what happened in DeFi today?'."
        ),
    )
    async def get_latest(
        lang: str = _DEFAULT_LANG,
        category: str | None = None,
        limit: int = _DEFAULT_LIMIT,
    ) -> dict[str, Any]:
        """Get latest news from the last 24h.
    
        Args:
            lang: BCP-47 language tag (default en-US).
            category: Optional category slug (see list_categories).
            limit: Max results (1-30, default 10).
        """
        async with ZippClient() as client:
            return await client.get_latest(lang=lang, category=category, limit=limit)
  • The MCP tool decorator registers 'get_latest' with its name and description. The schema is inferred from the function signature parameters (lang: str, category: str | None, limit: int).
    @mcp.tool(
        name="get_latest",
        description=(
            "Latest news from the last 24 hours. Optionally scoped to a "
            "category. Returns posts ordered newest-first. Use for 'what's "
            "new today?' or 'what happened in DeFi today?'."
        ),
    )
  • The @mcp.tool decorator registers 'get_latest' into the FastMCP server instance, making it available via MCP tool listing.
    @mcp.tool(
        name="get_latest",
        description=(
            "Latest news from the last 24 hours. Optionally scoped to a "
            "category. Returns posts ordered newest-first. Use for 'what's "
            "new today?' or 'what happened in DeFi today?'."
        ),
    )
  • Helper method on ZippClient that builds HTTP params and calls GET /api/v1/news/latest on the Zipp REST API to fetch the latest 24h news.
    async def get_latest(
        self,
        *,
        lang: str = "en-US",
        category: str | None = None,
        limit: int = 10,
    ) -> dict[str, Any]:
        params: dict[str, Any] = {"lang": lang, "limit": limit}
        if category:
            params["category"] = category
        return await self._get("/latest", params=params)
Behavior3/5

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

No annotations provided, so the description must carry behavioral info. It mentions temporal scope (24 hours) and ordering (newest-first), but omits details like authorization, rate limits, or caching 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?

Three concise sentences, front-loaded with core purpose, no redundancy or waste.

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

Completeness3/5

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

Output schema exists, but the description lacks parameter explanations and usage guidelines for alternatives, making it somewhat incomplete for a tool with 3 parameters and 0% schema coverage.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to compensate. It explains the category parameter's optional scoping but does not clarify 'lang' or 'limit' parameters, leaving their meaning implicit.

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 it retrieves latest news from the last 24 hours, optionally filtered by category, and returns posts newest-first. This distinguishes it from siblings like get_breaking, get_featured, and search.

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?

Provides concrete use cases ('what's new today?' and 'what happened in DeFi today?'), but does not explicitly contrast with alternatives or state when not to use.

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/deficlow/zipp-mcp'

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