Retrieve a Cricinfo team squad from a profile URL, returning recent player rosters with roles and withdrawal or overseas markers.
Get a Cricinfo team squad. Returns recent public squad announcements and player rosters from a Cricinfo team profile, including player roles and withdrawal or overseas markers when published.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Canonical Cricinfo team profile URL |
Changes observed during successful MCP inspections.
v1.16.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of behavioral disclosure. It does disclose useful behavioral details: results are 'recent public squad announcements,' and markers appear 'when published.' However, it does not address freshness, failure behavior, or whether the returned roster is current or historical.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded: the first sentence states the core action, and the second adds return-detail highlights. The slight redundancy between 'Get' and 'Returns' is minor and the text earns its length.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with no output schema, the description adequately explains what the caller gets: squads, rosters, roles, and conditional markers. It does not fully clarify distinctions from sibling Cricinfo tools, but the essential calling context is present.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents the single parameter 'url' as 'Canonical Cricinfo team profile URL,' giving 100% coverage. The description reinforces that the URL points to a team profile but adds no new parameter-level semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the resource ('Cricinfo team squad') and what is returned: recent squad announcements and player rosters with roles and withdrawal/overseas markers. It does not explicitly name a sibling tool for contrast, so it is clear but not fully differentiated by name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for retrieving a squad, but provides no guidance on when to prefer it over related tools like cricinfo_team, cricinfo_team_schedule, or roster tools from other sources. No alternatives or exclusion criteria are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.