Gully

Gully — connector documentation

• MCP endpoint: https://gully.connectorbay.com/mcp
• REST API: POST https://gully.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://gully.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://gully.connectorbay.com/health · Tool schemas: https://gully.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/gully · agent@connectorbay.com

What Gully is for

The question that comes up in every India-cricket conversation — who won the IPL that year, how many titles does this team actually have, what does DRS mean, what's a googly — answered without a scroll through ten different listicle sites, from one hand-curated, verified reference.

What it does

Every IPL season's champion and runner-up since the league began in 2008 (ipl_champions); a profile for each of the 11 franchises the league has fielded — city, home ground, founding year, every title and the year it came, notable captains, and a short history note (franchise_info, team_search); a title-count ranking (most_titles); every ICC ODI Cricket World Cup, T20 World Cup, and Champions Trophy winner and runner-up, plus title-count rankings by team (world_cup_winners); facts on ten major grounds — city, capacity, IPL home team, and a notable moment (venue_info); plain-language explainers for how Test, ODI and T20I cricket differ (format_explainer) and for specific rules like powerplay, DRS, DLS, the super over, follow-on, LBW, no-ball/wide and Mankading (rules_explainer); a glossary of common terms — googly, yorker, maiden over, strike rate, Orange Cap and more (cricket_glossary); and a multiple-choice trivia question generated fresh, on demand, straight from this same verified dataset rather than a separate question bank (trivia_quiz).

What it is not

Not a live scorecard or a ball-by-ball feed — Gully is a hand-curated reference, verified against public reporting as of the build date stated in its own data (ipl_champions and every other tool return that date). It won't tell you who's batting right now or what happened in yesterday's match, and record-holders for things like most IPL runs or wickets are deliberately left out rather than risk a stale or unverifiable number. For anything from the current season, live scores, or squad news, check an official source — ESPNcricinfo, the ICC, or BCCI/IPL.

Tools

IPL

ipl_champions — The IPL champion and runner-up for one season, or every season since the league began in 2008. Use for "who won the IPL in 2016", "list every IPL champion". Args: year.

franchise_info — One IPL franchise's profile: city, home ground, founding year, total titles and the years won, notable captains, and a short history note. Use for "tell me about Mumbai Indians", "what's RCB's history". Args: team.

team_search — Search IPL franchises by partial name, short code, or city. Use for "which team is based in Lucknow". Args: query.

most_titles — IPL franchises ranked by total titles won, with the years each title came. Use for "who has won the most IPL titles".

World Cups

world_cup_winners — Winners and runners-up of the ODI Cricket World Cup, T20 World Cup, or ICC Champions Trophy — one edition, the full list, or a title-count ranking by team. Use for "who won the 2011 World Cup", "how many T20 World Cups has India won". Args: format, year, rankings.

Reference

venue_info — A cricket ground's city, seating capacity, IPL home team (if any), and a notable fact. Use for "how big is the Narendra Modi Stadium", "which IPL team plays at Eden Gardens". Args: venue.

format_explainer — How Test, ODI and T20I cricket differ (overs, innings, duration). Use for "what's the difference between ODI and T20". Args: format.

rules_explainer — Plain-language explanations of specific cricket rules (powerplay, DRS, DLS/rain rule, super over, follow-on, LBW, no-ball/wide, Mankading). Use for "what's DRS", "explain the follow-on rule". Args: topic.

cricket_glossary — Definitions of common cricket terms (googly, yorker, maiden over, duck, strike rate, Orange/Purple Cap, ...). Use for "what does a googly mean", "what's the Orange Cap". Args: term.

Play

trivia_quiz — A fresh multiple-choice cricket trivia question, generated from this connector's own verified data (never a separate, harder-to-verify question bank). Use for "quiz me on cricket", "give me an IPL trivia question". Args: category, seed.

Conventions

• Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/gully/support

Gully — Privacy Policy

Effective 23 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Gully is. Gully is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated Indian cricket reference: IPL champions and franchise records, ICC World Cup winners, venues, rules, a glossary, and a trivia quiz. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.

What we receive. The arguments of each tool call — a year, a team name, a venue, a rule or glossary term, or a trivia category — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered from a bundled, hand-curated reference file and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Gully is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Gully — Terms of Service

Effective 23 September 2026. These terms govern use of the Gully connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Gully returns a hand-curated Indian cricket reference — IPL champions and franchise records, ICC World Cup and Champions Trophy winners, venues, rules, a glossary, and a trivia quiz — from data verified against public reporting at build time. It is accessed through an AI assistant or directly over MCP or HTTP.
2. Not a live scorecard, and not official. Gully is an independent reference tool, not affiliated with or endorsed by the BCCI, the IPL, the ICC, any franchise, or any player. It does not provide live scores, current standings, or squad news, and nothing in the Service should be relied on for wagering or fantasy-sport decisions.
3. Facts change. Records, titles and rules reflect public reporting as of the build date stated in the Service's own data; always check an official source (ESPNcricinfo, ICC, BCCI/IPL) for anything time-sensitive.
4. Acceptable use. Automated use within the published rate limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: your query is answered from a bundled reference file, and nothing is stored.
7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service. Our total liability is limited to US $100.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/gully

Gully support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://gully.connectorbay.com/mcp
• REST API: https://gully.connectorbay.com/openapi.json
• Live status: https://gully.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Gully never asks for them.