Skip to main content
Glama
arturogarrido

mcp-claudinho

by arturogarrido
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Knockout bracket

get_bracket
Read-only

Retrieve the 2026 World Cup knockout bracket from Round of 32 to final with live scores, filterable by stage, with structure-only fallback when live data is unavailable.

Instructions

Knockout bracket from the Round of 32 through the final, with live scores overlaid. Group slots project from live standings once a group has started; winner slots need a confirmed FT result. Pass an optional stage (R32, R16, QF, SF, 3P, F) to filter one round. Falls back to structure-only when live data is unavailable.

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)
stageNoKnockout round to show (omit for the full bracket)
flavorNoCommentary flair: off, subtle, full (default: full)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewYes
sourceNo
degradedNo
responseTruncatedNo
standingsDegradedNo
responseTruncationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.0
    • addedOutput schema / properties / responseTruncated
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / responseTruncation
      Added value: +{
+  "type": "string"
+}
  2. 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": {
+    "degraded": {
+      "type": "boolean"
+    },
+    "source": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "standingsDegraded": {
+      "type": "boolean"
+    },
+    "view": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "view"
+  ],
+  "type": "object"
+}
  3. Addedv0.8.4

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses meaningful runtime behavior: group slots project from live standings only after a group starts, winner slots require a confirmed FT result, and the tool falls back to structure-only when live data is unavailable. This is exactly the kind of non-obvious behavior an agent needs to know.

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?

Four short sentences each add a distinct fact: the bracket scope, live-data projection rules, stage filtering, and fallback behavior. There is no filler, repetition of schema details, or unnecessary preamble.

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 read-only annotations, full schema coverage, and presence of an output schema, the description covers all non-obvious behavior an agent needs: live-data dependencies, fallback mode, and optional round filtering. 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?

The schema already documents all four parameters with 100% coverage, so the description only needs to add value beyond that. It does so for the stage parameter by enumerating the round codes and stating that omitting it returns the full bracket; tz, lang, and flavor receive no additional prose, but the schema descriptions are sufficient.

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 description clearly identifies the resource as a knockout bracket from the Round of 32 through the final with live scores overlaid, which distinguishes it from standings or match tools. It lacks an explicit action verb like 'returns' or 'shows', but the tool name and noun phrase make the purpose unambiguous.

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

Usage Guidelines3/5

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

The description gives useful context about when data is available (group started, confirmed FT result) and how the optional stage parameter filters the bracket. However, it does not explicitly route the agent away from siblings like get_standings or get_live, so the choice between tools is left mostly to inference.

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

Deploy Server

Other Tools