Skip to main content
Glama

HSH Data-on-Demand

by io.github.hshintelligence
OverviewDiscussionsAdmin

hsh-cricket-parscore

Projected first-innings total for a men's T20, with a p10-p90 band, from the score you send. On 107 men's T20 internationals played after all its training data (1 Jul to 17 Sep 2026): median error 18.6 runs with a ground named and 18.5 without, and the final total fell inside the band 80% and 82% of the time. Per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
venueNoThe ground's name as scorecards write it; the answer says which ground was used.
wicketsYesWickets lost (0-10). At 10, or at 120 balls, the answer is the score itself.
cum_runsYesRuns scored so far.
balls_bowledYesLegal balls bowled, as a scorecard counts them: 1-120, and 12.3 overs = 75.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / balls_bowled / description
      Previous value: -""New value: +"Legal balls bowled, as a scorecard counts them: 1-120, and 12.3 overs = 75."
    • changedInput schema / properties / cum_runs / description
      Previous value: -""New value: +"Runs scored so far."
    • changedInput schema / properties / venue / description
      Previous value: -""New value: +"The ground's name as scorecards write it; the answer says which ground was used."
    • changedInput schema / properties / wickets / description
      Previous value: -""New value: +"Wickets lost (0-10). At 10, or at 120 balls, the answer is the score itself."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses model performance (median error, band coverage), training-data cutoff, and per-call framing. It does not mention side effects, but this is a read-only prediction tool and no such disclosure is necessary.

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?

The description is two sentences with no filler: the purpose is front-loaded, and the performance statistics are compact and relevant. 'Per call' is terse but meaningful.

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

Completeness4/5

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

For a simple prediction tool with a fully described schema, the description provides enough context: what it returns, its accuracy, and its data scope. It does not detail the exact response structure, but no output schema exists and the high-level description is sufficient for 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?

Schema description coverage is 100%, so the schema already documents all four parameters. The description adds little beyond the high-level 'from the score you send,' which is acceptable given the schema's completeness.

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 states a specific action ('Projected first-innings total') and resource ('men's T20') with a clear scope. It distinguishes itself from sibling cricket tools by focusing on first-innings par score rather than chase difficulty or win probability.

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

Usage Guidelines3/5

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

The description implies when to use it: when you have a current T20 score and want a projected first-innings total. However, it does not explicitly name alternatives or state when not to use it, leaving the agent to infer the boundary against sibling cricket tools.

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

All HSH Data-on-Demand toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources