Sports Rules
by gumballtools.com · remote · no sign-in to list tools · v0.1.0 · published by com.gumballtools
Work an offside call through IFAB Law 11 or NHL Rule 83, step by step.
2 tools: 1 change things and 1 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things1Claude Code: ask: see these tools
- Only reads1Claude Code: allow: see these tools
1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http sports-rules https://sports-rules.gumballtools.com/api/mcpFindings
Matches of fixed checks, with the text they matched.
- Infooffside
The description is 2,533 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ote IFAB or NHL rule text; it is copyrighted and this tool does not reproduce it."
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
2 tools
Changes things 1Claude Code: ask
offsideWork an offside call through the published decision procedure — association football under IFAB Law 11, or ice hockey under NHL Rule 83 — and return every step, not just the verdic…1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description is 2,533 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...ote IFAB or NHL rule text; it is copyrighted and this tool does not reproduce it."
Description, as the server wrote it Work an offside call through the published decision procedure — association football under IFAB Law 11, or ice hockey under NHL Rule 83 — and return every step, not just the verdict. Use this for any "was that offside" question in either sport. The two rules are structurally OPPOSITE and are routinely conflated, and there are four specific things that get answered wrong: SOCCER: 1. HANDS AND ARMS DO NOT COUNT, for anyone including goalkeepers. Only parts that could legally score are measured, and the boundary is the bottom of the armpit. This tool REFUSES to compute from an arm position rather than guessing where the shoulder was. 2. AN OFFSIDE POSITION IS NOT AN OFFENCE. It becomes one only with involvement in active play. Do not report "he was offside" when the answer is that he was in an offside position and uninvolved. `involvement` is REQUIRED once the geometry makes it decisive — the tool errors rather than assuming, so ask the user what the player actually did, and pass "none" if the answer is nothing. 3. No offside offence direct from a throw-in, goal kick, or corner. Absolute. 4. A DELIBERATE play by an opponent resets it; a deflection or a save does NOT. This is the distinction most arguments turn on. HOCKEY: 5. SKATES decide it. Not the stick, not the body. 6. Since 2021 a skate in the AIR above the blue line is still onside — the line is a plane, and ice contact is irrelevant. BUT this does not apply to tagging up on a delayed offside, where the skate must contact the line. Do not generalise the 2021 change to tag-ups. Input for soccer: positions along the attacking axis in metres, larger being nearer the opponents’ goal line — `attacker`, `ball`, `secondLastDefender`. Any consistent scale works; only the order matters. Optionally `restart`, `foremostPart`, `inOwnHalf`, `involvement`, `lastTouch`. Input for hockey: `rearSkate` in centimetres relative to the LEADING EDGE of the blue line, negative being the neutral-zone side. Optionally `skateOnIce`, `situation` (zone-entry or tag-up), and `stick`. Returns: a verdict of offside, onside, or no-offside-offence — three outcomes, not two, because "in an offside position but no offence" is a real and common answer — plus every step with the decisive one flagged, warnings, and a disclaimer. THIS IS NOT AN OFFICIAL RULING. Relay the steps, not just the verdict: in a real call the procedure is the easy half and the inputs are the argument. Do not quote IFAB or NHL rule text; it is copyrighted and this tool does not reproduce it.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 1Claude Code: allow
offside_rule_contrastReturn the structural differences between soccer offside and hockey offside, dimension by dimension.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Return the structural differences between soccer offside and hockey offside, dimension by dimension. Use this when someone asks how the two compare, or when you are about to reason about one sport using an intuition from the other — which is the commonest way to get either wrong. They differ on what part of the player is measured, when the picture freezes, whether position alone is an offence, what happens at exactly level, what resets the situation, and which restarts are exempt. Takes no arguments. Returns the comparison table.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http sports-rules https://sports-rules.gumballtools.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__sports-rules__offside_rule_contrast"
],
"ask": [
"mcp__sports-rules__offside"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as sports-rules. Review it before you use it.