Skip to main content
Glama

HSH Data-on-Demand

by io.github.hshintelligence
OverviewDiscussionsAdmin

hsh-cricket-momentum

Momentum & pressure index for a live T20 chase — quantifies which side is gaining (the swing signal) plus a pressure score. In-play trader signal. Pay per call via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currYesThe later state, same shape. A pair in the wrong order is refused before payment.
prevYesThe earlier state {balls_bowled, wickets, cum_runs}; balls_bowled is legal balls (12.3 overs = 75). A `target` inside it may be left out; if sent, it must equal the call's.
venueNoThe ground's name, applied to both states.
targetYesTarget to win.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / curr / description
      Previous value: -"Current state {balls_bowled, wickets, cum_runs, target}."New value: +"The later state, same shape. A pair in the wrong order is refused before payment."
    • changedInput schema / properties / prev / description
      Previous value: -"Prior state {balls_bowled, wickets, cum_runs, target}."New value: +"The earlier state {balls_bowled, wickets, cum_runs}; balls_bowled is legal balls (12.3 overs = 75). A `target` inside it may be left out; if sent, it must equal the call's."
    • addedInput schema / properties / venue
      Added value: +{
+  "description": "The ground's name, applied to both states.",
+  "type": "string"
+}
  2. Added

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full disclosure burden. It only adds 'Pay per call via x402,' and does not mention whether the call is read-only, what the returned index looks like, how to interpret the swing signal, or failure modes beyond what appears in the schema's parameter notes.

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 short sentences with the core output first, then use context, then billing. There is no filler, and every sentence contributes to selection or invocation.

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

Completeness3/5

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

For a no-output-schema tool with no annotations, the description leaves the output format and index interpretation unspecified. However, the parameter schema is unusually thorough, so the agent has enough information to construct a valid request even if it cannot predict the exact response.

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% and the parameter descriptions already detail prev, curr, target, and venue including edge cases like ball count and wrong-order refusal. The main description adds no parameter-specific meaning, so the baseline 3 applies.

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 identifies the resource as a 'Momentum & pressure index for a live T20 chase' and says it 'quantifies which side is gaining' along with a pressure score. This separates it from sibling tools like winprob or chase-difficulty by output type, though it stops short of naming any sibling explicitly.

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?

It gives clear context: it is for a live T20 chase and is an in-play trader signal, which tells an agent when this tool is relevant. It does not mention alternatives or exclusion conditions, so it lacks the explicit routing of a 5.

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