Skip to main content
Glama
arturogarrido

mcp-claudinho

by arturogarrido
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Live matches

get_live
Read-only

Get live in-play World Cup matches with current score and minute. Provides real-time state for matches currently being played.

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
NameRequiredDescriptionDefault
tzNoIANA timezone for kickoff times, e.g. America/Mexico_City
langNoLocale for dates, provider attribution, and commentary: en, es, pt, fr (the summary scaffold stays English; other locales fall back to en)
flavorNoCommentary flair: off, subtle, full (default: full)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
sourceYes
matchesYes
degradedYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv0.9.0
    • 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"
+}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds transparency by noting results include current score and minute, and that output is 'empty when nothing is live'. This goes beyond annotations in describing the return format and conditional behavior.

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 two sentences with no wasted words. Critical information (purpose, when to use, alternative) is front-loaded. Every sentence earns its place.

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?

Given the tool's low complexity (simple live matches), the presence of an output schema, and annotations covering safety and variability, the description is fully adequate. It covers purpose, usage guidance, parameter semantics, and edge case (empty when live).

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 coverage is 100%, so baseline is 3. The description adds value by stating 'tz/lang/flavor affect formatting only', clarifying that parameters do not affect data content or filtering. This is useful semantic guidance beyond the schema.

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 clearly states the tool returns 'only matches in play right now' with current score and minute, and distinguishes itself from sibling 'get_today' which includes upcoming and finished matches. The verb 'get' plus resource 'live' is specific and unambiguous.

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?

The description explicitly says 'Use during matches for in-play state; for a full day's schedule including upcoming and finished, use get_today.' This provides clear when-to-use and when-not-to-use guidance with a named alternative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arturogarrido/claudinho'

If you have feedback or need assistance with the MCP directory API, please join our Discord server