mcp-claudinho

Today's matches

get_today

Read-only

Retrieve a full day's football fixtures with live scores and minutes for matches in play, defaulting to today's date. Supports timezone, language, and commentary options.

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. 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 dates, attribution, and commentary (en/es/pt/fr); flavor sets commentary tone.

Input Schema

TableJSON 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, provider attribution, and commentary: en, es, pt, fr (the summary scaffold stays English; other locales fall back to en)
`flavor`	No	Commentary flair: off, subtle, full (default: full)

Output Schema

TableJSON Schema

Name	Required	Description
`date`	Yes
`count`	Yes
`source`	Yes
`matches`	Yes
`degraded`	Yes
`truncated`	Yes
`marketSignals`	No
`marketComplete`	No	False when optional market enrichment did not check every relevant fixture
`responseTruncated`	No
`responseTruncation`	No

Schema Changelog

Changes observed during successful MCP inspections.

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.7/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true, lowering the burden. The description adds valuable context beyond that: live score/minute overlay, the meaning of marketComplete=false as an incomplete read rather than absent signal, and locale/flavor behavior. This is strong supplementary behavioral disclosure, though it does not discuss data freshness or pagination.

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

Conciseness5/5

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

The description is dense but every sentence earns its place: core behavior first, sibling differentiation second, and parameter semantics third. It is well-structured and front-loaded without redundancy.

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, annotations covering safety/open-world semantics, and four optional parameters all documented in the schema, the description provides the remaining context needed: when to use the tool, what the live overlay means, how the marketComplete flag should be interpreted, and how parameters affect output. Nothing critical is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining that tz affects kickoff rendering, lang localizes dates/attribution/commentary, and flavor sets commentary tone. It also clarifies the marketComplete semantics relevant to prediction-market enrichment, which supports parameter understanding.

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 verb and resource ('All fixtures for a date') with a clear default of today. It also explicitly differentiates itself from sibling tools by describing scope as 'a whole day's card' and naming get_live, get_next_fixture, and get_match as alternatives for narrower queries.

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?

Provides explicit when-to-use guidance ('Use this for a whole day's card') and names the exact sibling tools to use for in-play matches, a single team's fixture, or single-match detail. This leaves no ambiguity about tool selection.

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

Deploy Server