Skip to main content
Glama
arturogarrido

mcp-claudinho

by arturogarrido
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Group standings

get_standings
Read-only

Fetch live 2026 World Cup group standings by group letter (A–L) or for all groups, showing played, W/D/L, goal difference, and points.

Instructions

Live cumulative group standings — pass a group letter A–L, or omit for all 12. Returns ranked rows (team, played, W/D/L, goal difference, points). Use get_today for fixtures/scores and get_next_fixture for one team. If unavailable, the default World Cup scope returns a roster at zero; competitions without a compatible bundled roster return no tables. Both are flagged degraded.

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)
groupNoGroup letter A–L (omit for all)
flavorNoCommentary flair: off, subtle, full (default: full)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYes
tablesYes
degradedYes
responseTruncatedNo
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"
+      ]
+    },
+    "tables": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "items": {
+            "$ref": "#/properties/tables/anyOf/0"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "degraded",
+    "source",
+    "tables"
+  ],
+  "type": "object"
+}
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark it read-only and open-world, and the description adds useful degraded behavior context: default scope returns a zero roster when unavailable, and incompatible competitions return no tables. This goes beyond the annotations, though it could define 'degraded' more concretely.

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 tight sentences, front-loaded with the core purpose and scope, followed by sibling routing and edge-case behavior. There is no filler or repetition of schema details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, full parameter documentation, and safety annotations, the description covers what the tool returns, how to scope it, sibling alternatives, and degraded-mode behavior. Minor gap: 'flagged degraded' is not fully explained, but this is a small omission given the rich structured context.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema carries the parameter meaning. The description reinforces group behavior ('omit for all 12') but adds no detail about tz, lang, or flavor beyond what the schema already provides.

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 exactly what the tool returns: live cumulative group standings with ranked rows (team, played, W/D/L, goal difference, points). It clearly distinguishes itself from siblings by naming get_today for fixtures/scores and get_next_fixture for team-specific info, so an agent can route correctly.

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 explains how to scope the call (pass a group letter or omit for all 12) and names the alternatives for related use cases. This gives the agent clear when-to-use-this vs use-that guidance.

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