`cricsheet_chase_search`

Pack: cricsheet · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/cricsheet_chase_search for the schema, then POST the same URL with its arguments for the data.

Find ODI/T20I/IPL chases by result, wickets and balls remaining, date, tournament.

Tool description as the model sees it

Compound cricket match search on the second innings (the chase): filter limited-overs matches (ODI, T20I, IPL) by whether the side batting second won or lost, wickets remaining and balls remaining at the end of the chase, date range, season, tournament/event, team, gender and format. Each hit returns target, chase score, wickets lost, balls used, wickets_remaining (10 minus wickets lost) and balls_remaining (scheduled overs minus legal balls bowled; null for rain-affected matches decided by a method such as DLS). Example: T20I chases won with 5+ wickets and 10+ balls to spare since 2024. Source: Cricsheet match data (ODC-BY). Tests are excluded.

Parameters

Name	Type	Required	Description
`second_innings_result`	string	no	Did the side batting second win? Default “won” (a successful chase).
`format`	string	no	Match format: “ODI”, “T20I” or “IPL”. Omit for all three.
`min_wickets_remaining`	number	no	Chasing side had at least this many wickets in hand at the end (0-10).
`max_wickets_remaining`	number	no	Chasing side had at most this many wickets in hand at the end (0-10).
`min_balls_remaining`	number	no	At least this many legal balls unused at the end of the chase (assumes full scheduled overs; 120 in T20, 300 in ODI).
`max_balls_remaining`	number	no	At most this many legal balls unused (0 = chase went to the last ball).
`team`	string	no	Chasing team name as Cricsheet uses it, e.g. “India”.
`gender`	string	no	Men’s or women’s cricket.
`season`	string	no	Season label, e.g. “2024” or “2023/24”.
`event`	string	no	Tournament/event name or fragment, e.g. “World Cup” or “Indian Premier League”.
`date_from`	string	no	Earliest match date, YYYY-MM-DD.
`date_to`	string	no	Latest match date, YYYY-MM-DD.
`limit`	number	no	Max matches to return, 1-200. Default 25.
`offset`	number	no	Pagination offset. Default 0.

Example call

Arguments

{
  "format": "T20I",
  "second_innings_result": "won",
  "min_wickets_remaining": 5,
  "min_balls_remaining": 10,
  "date_from": "2024-01-01",
  "limit": 5
}

curl

curl -X POST https://gateway.pipeworx.io/cricsheet/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"cricsheet_chase_search","arguments":{"format":"T20I","second_innings_result":"won","min_wickets_remaining":5,"min_balls_remaining":10,"date_from":"2024-01-01","limit":5}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('cricsheet_chase_search', {
  "format": "T20I",
  "second_innings_result": "won",
  "min_wickets_remaining": 5,
  "min_balls_remaining": 10,
  "date_from": "2024-01-01",
  "limit": 5
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}

Connect to just the cricsheet pack

{
  "mcpServers": {
    "cricsheet": {
      "url": "https://gateway.pipeworx.io/cricsheet/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

cricsheet_chase_search