Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cricbuzz_navigation

Fetch Cricbuzz top-level menus and dropdown links as a JSON-LD navigation tree from the Live Scores page, covering News, Videos, Rankings, More, and utility links.

Instructions

Discover Cricbuzz top-level menus and dropdown links. Returns the current first-party JSON-LD navigation tree from the Live Scores page, including the News, Videos, Rankings, and More dropdown items and utility links. The short featured Team and Series dropdown entries are not complete directories; use the teams and series endpoints for their full dynamic lists.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full disclosure burden and does: it names the data source ('current first-party JSON-LD navigation tree from the Live Scores page'), describes the shape of what is returned, and flags a real limitation about incomplete Team/Series entries. It reads as a non-mutating discovery call, which is the behavior an agent needs to assume.

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 sentences, front-loaded with the action and resource, followed by what is returned and then the exclusion. There is no filler; each sentence adds distinct information.

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

Completeness5/5

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

For a zero-param navigation tool with no output schema, the description explains source, contents, and scope limits, which is everything needed to call it correctly. No return-value documentation is missing that would change the agent's decision.

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?

Zero parameters, so the baseline is 4 and nothing is left ambiguous. The description correctly implies that no arguments are required, letting the agent invoke it immediately.

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?

States a specific verb and resource: 'Discover Cricbuzz top-level menus and dropdown links', then names the concrete contents (News, Videos, Rankings, More, utility links). An agent can distinguish this from cricbuzz_teams or cricbuzz_series without opening any schema.

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

Usage Guidelines5/5

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

Explicitly warns that the featured Team and Series dropdown entries are not complete directories and routes the agent to the teams and series endpoints for full lists. That is a concrete when-not plus named alternatives, not just implied navigation use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools