mcp-claudinho

Shareable match snippet

get_share_snippet

Read-only

Create ready-to-paste World Cup share cards for fixtures, standings, brackets, and live matches, returning both snippet and structured data.

Instructions

A polished, copy-pasteable card (plain text) for a match (matchId), a team's next fixture (team), a group's standings table (group, e.g. "A"), the knockout bracket (bracket: true), a date (default: today), or live matches (live: true). Returns the ready-to-paste snippet plus structured data — hand the snippet text to the user verbatim. marketComplete:false is stated inside the card as an incomplete optional read. No links; it carries a non-affiliation disclaimer, and any market line stays informational only.

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)
`live`	No	Snapshot of matches in play right now
`team`	No	3-letter team code for that team's next fixture, e.g. MEX
`group`	No	Group letter A–L for a standings card, e.g. A
`style`	No	social (default, full card) or compact (one line per match)
`flavor`	No	Commentary flair: off, subtle, full (default: full)
`bracket`	No	Knockout bracket card (use with optional knockoutStage)
`matchId`	No	Match id (most specific)
`knockoutStage`	No	Filter the bracket card to one round
`includeHashtag`	No	Include the #VibingLaVidaLoca tag (default true)
`includeMarkets`	No	Include the reliable market line when available (default true)
`includeInstallLine`	No	Include the "Try it: …" run cue (default true)

Output Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes
`team`	No
`view`	No
`count`	No
`group`	No
`stage`	No
`style`	No
`source`	No
`tables`	No
`target`	No
`matches`	No
`snippet`	No
`degraded`	No
`truncated`	No
`marketSignals`	No
`marketComplete`	No	False when optional market enrichment did not check every relevant fixture
`informationalOnly`	No
`responseTruncated`	No
`responseTruncation`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.10.0Sep 15, 2026

addedOutput schema / properties / count
```
Added value: +{
+  "type": "number"
+}
```

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

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": {
+    "degraded": {
+      "type": "boolean"
+    },
+    "group": {
+      "type": "string"
+    },
+    "informationalOnly": {
+      "type": "boolean"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "marketSignals": {
+      "additionalProperties": {
+        "$ref": "#/properties/tables/anyOf/0"
+      },
+      "type": "object"
+    },
+    "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"
+    },
+    "snippet": {
+      "type": "string"
+    },
+    "source": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "stage": {
+      "type": "string"
+    },
+    "style": {
+      "type": "string"
+    },
+    "tables": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "items": {
+            "$ref": "#/properties/tables/anyOf/0"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "target": {
+      "type": "string"
+    },
+    "team": {
+      "type": "string"
+    },
+    "view": {
+      "anyOf": [
+        {
+          "$ref": "#/properties/tables/anyOf/0"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "kind"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv0.8.4Jun 24, 2026

addedInput schema / properties / bracket

Added value: +{
+  "description": "Knockout bracket card (use with optional knockoutStage)",
+  "type": "boolean"
+}

addedInput schema / properties / knockoutStage

Added value: +{
+  "description": "Filter the bracket card to one round",
+  "enum": [
+    "R32",
+    "R16",
+    "QF",
+    "SF",
+    "3P",
+    "F"
+  ],
+  "type": "string"
+}

Changed1 schema field changedv0.5.0Jun 14, 2026

addedInput schema / properties / group

Added value: +{
+  "description": "Group letter A–L for a standings card, e.g. A",
+  "pattern": "^[A-La-l]$",
+  "type": "string"
+}

First observedv0.1.0Jun 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds valuable behavioral details beyond the readOnlyHint/openWorldHint annotations: it notes that marketComplete:false is stated inside the card, that no links are included, a non-affiliation disclaimer is present, and market lines are informational only. This transparency about the output's nature and limitations is not required by annotations but is very useful for an agent deciding how to present the result.

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 compact—three sentences—and front-loads the core purpose ('polished, copy-pasteable card') before enumerating input modes. Every sentence adds value: the purpose, the verbatim-handing instruction, and the transparency caveats. No fluff.

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 complexity (14 optional parameters, 100% schema coverage, and an output schema), the description sufficiently covers when to use it, what it produces, and important output characteristics (no links, disclaimer, informational market lines). The instruction to hand the snippet verbatim is critical and present. Nothing essential is missing.

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 each parameter is documented in the schema. The description enhances this by mapping parameters to card types (e.g., 'team' for next fixture, 'group' for standings, 'bracket: true' for knockout), and clarifies defaults like date=today. It also ties includeMarkets to the informational market line context, adding meaning beyond raw schema definitions.

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 produces a polished, copy-pasteable card for various match data types (match, team fixture, group standings, bracket, date, live), with a specific verb ('returns a card') and resource ('shareable snippet'). It differentiates from sibling tools by focusing on the ready-to-paste output, making it unambiguous what this tool does.

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

Usage Guidelines4/5

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

The description enumerates the exact input scenarios (matchId, team, group, bracket, date, live) and instructs to hand the snippet text verbatim to the user, giving clear usage context. It does not explicitly contrast with sibling tools like get_match or get_standings, but the purpose is distinct enough that an agent would infer when to use this tool for a shareable card.

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

Deploy Server