mcp-claudinho

Live matches

get_live

Read-only

Fetch only matches currently in play with live score and minute for in-play state; use get_today for full schedules. An empty list means no match is in play only when the read is whole.

Instructions

Only matches in play right now, each with current score and minute; an empty list means nothing is in play only when the read was whole (neither partial nor degraded says otherwise). Off the World Cup, betweenEditions means the competition's edition has ended and the next has not started. partial means the provider sent records that could not be used: an empty list then means no match in play could be read, not that none is. Use during matches for in-play state; for a full day's schedule including upcoming and finished, use get_today. tz/lang/flavor affect formatting only.

Input Schema

Name	Required	Description
`tz`	No	IANA timezone for kickoff times, e.g. America/Mexico_City
`lang`	No	Locale for dates, list titles, match status and stage words, a match timeline's kind words (Goal, Yellow card…), the empty and outage sentences, provider attribution, and commentary: en, es, pt or fr (no other value is supported). Without it, or when it is empty, the server's CLAUDINHO_LANG when that is exactly one of the four, else en. The market copy, a few notes and the disclaimer stay English
`flavor`	No	Commentary flair: off, subtle, full (default: full)
`competition`	No	The competition: an alias such as premier-league, or an ESPN slug such as eng.1 (list_competitions lists the aliases). Without it: the server's CLAUDINHO_COMPETITION, else the user's saved choice (claudinho follow); with none, the answer is noCompetition

Output Schema

Name	Required	Description
`count`	Yes
`source`	Yes
`matches`	Yes
`partial`	No	Present when the provider sent records that could not be used: what is returned is what was read, and may not be the whole answer (absence is not elimination). omitted is how many provider records were left out, when known; they may have lain outside what was asked for, so the count is a bound, not a loss
`degraded`	Yes
`truncated`	Yes
`competition`	No	The competition this answer is for: its ESPN slug, its alias, its name, where the choice came from (flag: the competition argument; env: the server's CLAUDINHO_COMPETITION; saved: the user's saved choice, claudinho follow), and experimental for a slug the supported table does not hold; null with noCompetition when nothing is chosen
`unknownTeam`	No	Present (true) when the roster the competition has holds no team by that name: the bundled nations on the World Cup; the table read whole and the next 14 days' fixtures elsewhere (a claim about that evidence, not the whole competition: a club out in a qualifying round is in no table). Never stated when the table or the span could not be read whole
`unsupported`	No	Present (true) when this is not available for this competition yet; an empty result then means "unsupported", not "none found"
`inapplicable`	No	Present (true) when this competition has no such thing at all (a league season with no knockout tie has no knockout tree)
`noCompetition`	No	Present (true) when no competition is chosen (no competition argument, no server CLAUDINHO_COMPETITION, no saved choice): nothing was read, competition is null, and the text says what to do (pass competition, or the user runs claudinho follow <alias>)
`rosterEvidence`	No	With unknownTeam: the evidence it rests on, the competition's table and span (table) or the World Cup's bundled nations (bundle)
`betweenEditions`	No	Present when the competition is between editions: the edition named by label ended on ended (the provider's calendar day, YYYY-MM-DD, the season end it states), and nothing in the read is scheduled or in play
`rosterIncomplete`	No	Present (true) when the competition's roster could not be read whole and the name could not be resolved without it (no match, or only by a code or a partial name); not an outage: ask with the club's full name
`responseTruncated`	No
`responseTruncation`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.13.1Oct 30, 2026

changedInput schema / properties / lang / description

Previous value: -"Locale for dates, list titles, match status and stage words, a match timeline's kind words (Goal, Yellow card…), the empty and outage sentences, provider attribution, and commentary: en, es, pt, fr (the market copy, a few notes and the disclaimer stay English; other locales fall back to en)"New value: +"Locale for dates, list titles, match status and stage words, a match timeline's kind words (Goal, Yellow card…), the empty and outage sentences, provider attribution, and commentary: en, es, pt or fr (no other value is supported). Without it, or when it is empty, the server's CLAUDINHO_LANG when that is exactly one of the four, else en. The market copy, a few notes and the disclaimer stay English"

Changed14 schema fields changedv0.12.0Oct 18, 2026

addedInput schema / properties / competition

Added value: +{
+  "description": "The competition: an alias such as premier-league, or an ESPN slug such as eng.1 (list_competitions lists the aliases). Without it: the server's CLAUDINHO_COMPETITION, else the user's saved choice (claudinho follow); with none, the answer is noCompetition",
+  "type": "string"
+}

changedInput schema / properties / lang / description

Previous value: -"Locale for dates, provider attribution, and commentary: en, es, pt, fr (the summary scaffold stays English; other locales fall back to en)"New value: +"Locale for dates, list titles, match status and stage words, a match timeline's kind words (Goal, Yellow card…), the empty and outage sentences, provider attribution, and commentary: en, es, pt, fr (the market copy, a few notes and the disclaimer stay English; other locales fall back to en)"

addedOutput schema / properties / betweenEditions

Added value: +{
+  "additionalProperties": false,
+  "description": "Present when the competition is between editions: the edition named by label ended on ended (the provider's calendar day, YYYY-MM-DD, the season end it states), and nothing in the read is scheduled or in play",
+  "properties": {
+    "ended": {
+      "type": "string"
+    },
+    "label": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ended"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / competition

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "properties": {
+        "alias": {
+          "type": "string"
+        },
+        "chosenBy": {
+          "enum": [
+            "flag",
+            "env",
+            "saved"
+          ],
+          "type": "string"
+        },
+        "experimental": {
+          "const": true,
+          "type": "boolean"
+        },
+        "name": {
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "slug",
+        "name",
+        "chosenBy"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The competition this answer is for: its ESPN slug, its alias, its name, where the choice came from (flag: the competition argument; env: the server's CLAUDINHO_COMPETITION; saved: the user's saved choice, claudinho follow), and experimental for a slug the supported table does not hold; null with noCompetition when nothing is chosen"
+}

addedOutput schema / properties / inapplicable

Added value: +{
+  "const": true,
+  "description": "Present (true) when this competition has no such thing at all (a league season with no knockout tie has no knockout tree)",
+  "type": "boolean"
+}

addedOutput schema / properties / matches / items / properties / events

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "added": {
+        "type": "number"
+      },
+      "minute": {
+        "type": "number"
+      },
+      "player": {
+        "type": "string"
+      },
+      "side": {
+        "type": "string"
+      },
+      "teamCode": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / matches / items / properties / home / properties / id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / matches / items / properties / stageLabel
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / noCompetition

Added value: +{
+  "const": true,
+  "description": "Present (true) when no competition is chosen (no competition argument, no server CLAUDINHO_COMPETITION, no saved choice): nothing was read, competition is null, and the text says what to do (pass competition, or the user runs claudinho follow <alias>)",
+  "type": "boolean"
+}

addedOutput schema / properties / partial

Added value: +{
+  "additionalProperties": false,
+  "description": "Present when the provider sent records that could not be used: what is returned is what was read, and may not be the whole answer (absence is not elimination). omitted is how many provider records were left out, when known; they may have lain outside what was asked for, so the count is a bound, not a loss",
+  "properties": {
+    "omitted": {
+      "exclusiveMinimum": 0,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / rosterEvidence

Added value: +{
+  "description": "With unknownTeam: the evidence it rests on, the competition's table and span (table) or the World Cup's bundled nations (bundle)",
+  "enum": [
+    "table",
+    "bundle"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / rosterIncomplete

Added value: +{
+  "const": true,
+  "description": "Present (true) when the competition's roster could not be read whole and the name could not be resolved without it (no match, or only by a code or a partial name); not an outage: ask with the club's full name",
+  "type": "boolean"
+}

addedOutput schema / properties / unknownTeam

Added value: +{
+  "const": true,
+  "description": "Present (true) when the roster the competition has holds no team by that name: the bundled nations on the World Cup; the table read whole and the next 14 days' fixtures elsewhere (a claim about that evidence, not the whole competition: a club out in a qualifying round is in no table). Never stated when the table or the span could not be read whole",
+  "type": "boolean"
+}

addedOutput schema / properties / unsupported

Added value: +{
+  "const": true,
+  "description": "Present (true) when this is not available for this competition yet; an empty result then means \"unsupported\", not \"none found\"",
+  "type": "boolean"
+}

Changed4 schema fields changedv0.10.0Sep 15, 2026

addedOutput schema / properties / responseTruncated
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / responseTruncation
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "degraded",
-  "source",
-  "count",
-  "matches"
-]New value: +[
+  "degraded",
+  "source",
+  "count",
+  "truncated",
+  "matches"
+]

Changed2 schema fields changedv0.9.0Jul 3, 2026

changedInput schema / properties / lang / description

Previous value: -"Locale for formatting: en, es, pt, fr (other locales fall back to en)"New value: +"Locale for dates, provider attribution, and commentary: en, es, pt, fr (the summary scaffold stays English; other locales fall back to en)"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "degraded": {
+      "type": "boolean"
+    },
+    "matches": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "away": {
+            "$ref": "#/properties/matches/items/properties/home"
+          },
+          "group": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "home": {
+            "additionalProperties": true,
+            "properties": {
+              "code": {
+                "type": "string"
+              },
+              "flag": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "id": {
+            "type": "string"
+          },
+          "kickoff": {
+            "type": "string"
+          },
+          "minute": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "score": {
+            "anyOf": [
+              {
+                "additionalProperties": true,
+                "properties": {
+                  "away": {
+                    "type": "number"
+                  },
+                  "home": {
+                    "type": "number"
+                  }
+                },
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "shootout": {
+            "$ref": "#/properties/matches/items/properties/score/anyOf/0"
+          },
+          "stage": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "venue": {
+            "type": "string"
+          },
+          "winnerCode": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "source": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "degraded",
+    "source",
+    "count",
+    "matches"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jun 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover safety (readOnly) and open-world access, yet the description adds substantial context they don't: empty-list semantics gated on whole vs partial/degraded reads, and the betweenEditions off-World-Cup case. The phrasing of the empty-list rule is convoluted ('nothing is in play only when the read was whole (neither partial nor degraded says otherwise)'), which slightly undercuts an otherwise rich disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded and nothing is padded for length, but the parenthetical about partial/degraded reads is grammatically tangled and forces re-reading to decode the empty-list guarantee. Density here costs comprehension rather than saving words.

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

Completeness5/5

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

An output schema exists, so return values need not be explained. The description covers what an agent actually needs to interpret results correctly: in-play scope, empty-list meaning under whole vs degraded reads, and the off-season case.

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 coverage is 100%, so tz, lang, flavor and competition are already documented in detail far beyond what the description says. The one addition, 'tz/lang/flavor affect formatting only,' is useful for scoping their impact but marginal. Baseline 3 is appropriate.

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?

States a specific resource and scope: matches in play right now, each with current score and minute. It distinguishes itself from get_today by naming that sibling and its different scope, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('Use during matches for in-play state') and the alternative with its selection condition ('for a full day's schedule including upcoming and finished, use get_today'). The routing decision is fully specified.

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

Deploy Server

Live matches

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools