Skip to main content
Glama

search

Search Zipp's news catalogue for recent stories on a topic, ordered by recency. Ideal for finding crypto news like updates on Bitcoin ETFs or Solana hacks.

Instructions

Full-text search across Zipp's news catalogue. Returns recent matching stories ordered by recency (with relevance as a tiebreaker). Use for questions like 'what's happening with Bitcoin ETFs?' or 'find news about Solana hacks'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
langNoen-US
categoryNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'search'. Decorated with @mcp.tool(name='search'), accepts query, lang, category, limit params, delegates to ZippClient.search().
    @mcp.tool(
        name="search",
        description=(
            "Full-text search across Zipp's news catalogue. Returns recent "
            "matching stories ordered by recency (with relevance as a "
            "tiebreaker). Use for questions like 'what's happening with "
            "Bitcoin ETFs?' or 'find news about Solana hacks'."
        ),
    )
    async def search(
        query: str,
        lang: str = _DEFAULT_LANG,
        category: str | None = None,
        limit: int = _DEFAULT_LIMIT,
    ) -> dict[str, Any]:
        """Search Zipp news.
    
        Args:
            query: Search query string (free text, supports ticker synonyms like BTC ↔ Bitcoin).
            lang: BCP-47 language tag. Search is language-locked — TR query → TR results only.
            category: Optional category slug to scope results (see list_categories).
            limit: Max results (1-30, default 10).
        """
        async with ZippClient() as client:
            return await client.search(
                query=query, lang=lang, category=category, limit=limit
            )
  • ZippClient.search() — builds query params and calls _get('/search', ...) which sends GET /api/v1/news/search to the Zipp REST API.
    async def search(
        self,
        *,
        query: str,
        lang: str = "en-US",
        category: str | None = None,
        limit: int = 10,
    ) -> dict[str, Any]:
        params: dict[str, Any] = {"query": query, "lang": lang, "limit": limit}
        if category:
            params["category"] = category
        return await self._get("/search", params=params)
  • Tool registration via FastMCP @mcp.tool() decorator with name='search' and description.
    @mcp.tool(
        name="search",
        description=(
            "Full-text search across Zipp's news catalogue. Returns recent "
            "matching stories ordered by recency (with relevance as a "
            "tiebreaker). Use for questions like 'what's happening with "
            "Bitcoin ETFs?' or 'find news about Solana hacks'."
        ),
Behavior3/5

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

Discloses ordering (recency with relevance tiebreaker) and recency of results, but no annotations exist so description should also mention that it is a read operation and any rate limits or other constraints.

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, no wasted words, front-loaded with purpose, highly concise.

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 output schema exists, return info is partially covered, but 4-parameter search tool with 0% schema coverage requires more parameter guidance than provided.

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?

With 0% schema description coverage, the description must compensate but only implies the 'query' parameter via 'full-text search'. Does not explain 'lang', 'category', or 'limit', leaving agent guessing.

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?

Description clearly states verb 'search' and resource 'news catalogue', distinguishing it from siblings like get_breaking or get_featured which target specific subsets.

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 examples of questions ('what's happening with Bitcoin ETFs?') that indicate when to use, but does not explicitly exclude cases or mention alternatives.

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