mcp-claudinho

Today's matches

get_today

Read-only

Fetch all fixtures for a given date (default today), with live score and minute overlaid on in-play matches. Use for a full day's card, not for single-match detail.

Instructions

All fixtures for a date (default: today), with live score and minute overlaid on any match in play. Optional prediction-market enrichment carries marketComplete; false means the read was incomplete, not that no signal exists. Off the World Cup, betweenEditions means the competition's edition ended before that date. partial means the provider sent records that could not be used: on the World Cup a fixture may then show from the bundled schedule without its live state (the text counts them, and names no provider when none shown was served), and where no bundled schedule was merged, an empty day means no fixture could be read for it, not that none is scheduled. Use this for a whole day's card; for only in-play matches use get_live, for one team's match use get_next_fixture, for a single match's detail use get_match. Kickoffs render in tz; lang localizes the title, dates, status and stage words, the empty and outage sentences, attribution, and commentary (en/es/pt/fr); flavor sets commentary tone.

Input Schema

Name	Required	Description
`tz`	No	IANA timezone for kickoff times, e.g. America/Mexico_City
`date`	No	Date as YYYY-MM-DD (default: today)
`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, fr (the market copy, a few notes and the disclaimer stay English; other locales fall back to en)
`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
`date`	Yes
`count`	Yes
`served`	No	The shown fixtures whose record the provider's window held; a shown fixture not among them is the bundled schedule's row, its live state unconfirmed
`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)
`marketSignals`	No
`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>)
`marketComplete`	No	False when optional market enrichment did not check every relevant fixture
`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.

Changed15 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 / served

Added value: +{
+  "description": "The shown fixtures whose record the provider's window held; a shown fixture not among them is the bundled schedule's row, its live state unconfirmed",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

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"
+}

Changed5 schema fields changedv0.10.0Sep 15, 2026

addedOutput schema / properties / marketComplete

Added value: +{
+  "description": "False when optional market enrichment did not check every relevant fixture",
+  "type": "boolean"
+}

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: -[
-  "date",
-  "degraded",
-  "source",
-  "count",
-  "matches"
-]New value: +[
+  "date",
+  "degraded",
+  "source",
+  "count",
+  "truncated",
+  "matches"
+]

Addedv0.9.0Jul 3, 2026
Removedv0.8.15Jul 1, 2026
First observedv0.1.0Jun 11, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only declare readOnly/openWorld, so the description carries real weight and delivers: live score and minute overlay, marketComplete=false meaning an incomplete read rather than absent signal, betweenEditions semantics, and a candid account of 'partial' where bundled-schedule fixtures can appear without live state and an empty day is ambiguous rather than confirmed empty. This is exactly the kind of degraded-data disclosure an agent needs to avoid misreporting.

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 purpose is front-loaded, but the body is a dense run-on chain of parentheticals and semicolon-clause caveats that is hard to parse on a single read. Most sentences do convey load-bearing edge-case information, but the packaging is heavier than it needs to be.

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?

With an output schema present, return-value explanation is unnecessary, and the description covers the remaining risk surface: empty-day ambiguity, degraded reads, parameter effects and sibling routing. An agent can call this correctly and interpret an empty or partial result without guessing.

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 schema already spells out tz, date format, lang locales and affected surfaces, and the competition alias/default chain. The description largely restates those (tz renders kickoffs, lang localizes, flavor sets tone) rather than adding new constraints, so per the high-coverage baseline a 3 is appropriate.

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 opening clause states a concrete scope — all fixtures for a date, defaulting to today — and the routing sentence explicitly separates it from get_live, get_next_fixture and get_match. It loses a point because the purpose is entangled with live-score and market-enrichment detail, and the title ('Today's matches') is narrower than the actual scope (any date).

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?

It gives an explicit selection rule ('Use this for a whole day's card') plus three named alternatives each paired with the condition that selects them (in-play only, one team, single match detail). No inference is required to pick the right sibling.

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

Deploy Server