mcp-claudinho

Live matches

get_live

Read-only

Get current score and minute for in-progress World Cup matches. Returns only live matches; empty when nothing is playing.

Instructions

Only matches in play right now — each with current score and minute (empty when nothing is live). 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

TableJSON Schema

Name	Required	Description
`tz`	No	IANA timezone for kickoff times, e.g. America/Mexico_City
`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	Default
`count`	Yes
`source`	Yes
`matches`	Yes
`degraded`	Yes
`truncated`	Yes
`responseTruncated`	No
`responseTruncation`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Behavior5/5

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

Annotations declare readOnlyHint and openWorldHint. The description adds valuable behavioral context: empty when nothing is live, and that tz/lang/flavor affect formatting only (not the match set). This goes beyond the annotations without contradicting them.

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?

Two sentences: first sentence front-loads the core behavior and empty case; second sentence gives usage guidance and param note. No wasted words, perfectly structured.

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?

Complete for a read-only list tool. It covers usage, empty response, param scope, and points to the sibling for alternative cases. Output schema exists, so return details need not be repeated. Annotations cover safety profile.

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 covers all 3 parameters with detailed descriptions. The description adds the crucial semantic that these parameters affect only formatting, not data selection – a non-obvious behavior that prevents misuse. This elevates it above the schema-only baseline.

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?

The description states exactly what the tool does: returns only matches currently in play, with current score and minute. It also clarifies the empty response case when nothing is live. This clearly distinguishes it from siblings like get_today.

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?

Explicitly states when to use (during matches for in-play state) and names the alternative (get_today) for a full day's schedule including upcoming and finished matches. No ambiguity remains.

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

Deploy Server