Skip to main content
Glama
tarun7r

cricket-mcp-server

search_live_commentary

Fetch real-time cricket match commentary and updates by entering match details or team names, providing instant web search results for live match insights.

Instructions

Search for live commentary and updates for cricket matches on the web.

Args: match_description (str, optional): Full match description (e.g., "Zimbabwe vs New Zealand 2nd Test") team1 (str, optional): First team name team2 (str, optional): Second team name

Returns: list: Web search results for live commentary and match updates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
match_descriptionNo
team1No
team2No

Implementation Reference

  • The handler function for the 'search_live_commentary' tool. It is decorated with @mcp.tool(), which handles both registration and schema definition via type hints. The function constructs a search query and uses the 'web_search' tool to find live commentary from Cricbuzz, ESPN Cricinfo, and general web results.
    @mcp.tool()
    def search_live_commentary(match_description: str = None, team1: str = None, team2: str = None) -> list:
        """
        Search for live commentary and updates for cricket matches on the web.
        
        Args:
            match_description (str, optional): Full match description (e.g., "Zimbabwe vs New Zealand 2nd Test")
            team1 (str, optional): First team name
            team2 (str, optional): Second team name
            
        Returns:
            list: Web search results for live commentary and match updates
        """
        if not match_description and not (team1 and team2):
            return [{"error": "Please provide either match_description or both team1 and team2"}]
        
        # Build search query
        if match_description:
            query = f"live commentary {match_description} cricket"
        else:
            query = f"live commentary {team1} vs {team2} cricket"
        
        # Search with cricket news sites
        results = []
        
        # Try Cricbuzz
        cricbuzz_results = web_search(query, num_results=3, site_filter="cricbuzz.com")
        if cricbuzz_results and "error" not in cricbuzz_results[0]:
            results.extend(cricbuzz_results)
        
        # Try ESPN Cricinfo
        espn_results = web_search(query, num_results=3, site_filter="espncricinfo.com")
        if espn_results and "error" not in espn_results[0]:
            results.extend(espn_results)
        
        # General search
        general_results = web_search(query, num_results=5)
        if general_results and "error" not in general_results[0]:
            results.extend(general_results)
        
        return results[:10]  # Limit to 10 results
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool performs a web search and returns results, but it doesn't cover critical aspects like whether it's read-only (implied by 'search' but not explicit), rate limits, authentication needs, or what happens with partial/no inputs. For a search tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 and appropriately sized, with a clear purpose statement followed by separate 'Args' and 'Returns' sections. Every sentence adds value, and there's no redundant information. It could be slightly more concise by integrating the sections more fluidly, but overall it's efficient and front-loaded.

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 the complexity of a search tool with 3 parameters, 0% schema description coverage, no annotations, and no output schema, the description is incomplete. It covers the basic purpose and parameters but lacks behavioral details, usage guidelines, and output specifics (e.g., result format, error handling). For a tool that interacts with web data, this leaves too many unknowns for reliable agent invocation.

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?

The description includes an 'Args' section that lists three optional parameters with brief examples (e.g., 'Zimbabwe vs New Zealand 2nd Test'), adding meaning beyond the input schema, which has 0% description coverage. However, it doesn't fully compensate for the schema gap—it lacks details on parameter interactions, format constraints, or how searches work with multiple/partial inputs. With 3 parameters at 0% schema coverage, the description provides basic but incomplete semantic 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 tool's purpose: 'Search for live commentary and updates for cricket matches on the web.' It specifies the verb ('search'), resource ('live commentary and updates'), and domain ('cricket matches on the web'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'get_live_commentary' or 'web_search', which prevents a perfect score.

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 versus alternatives. It doesn't mention sibling tools like 'get_live_commentary' (which might fetch commentary directly without web search) or 'web_search' (a general search tool), nor does it specify prerequisites or exclusions. Usage is implied by the purpose but lacks explicit context.

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

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