Skip to main content
Glama

Football Database and Results

by io.fdb4
OverviewDiscussionsAdmin

Team profile and draw statistics

get_team
Read-onlyIdempotent

[FREE] One team's profile and its all-time draw statistics.

Returns the team's name, country and type alongside the numbers this database is built on: matches played, draws, draw percentage, the no-draw streak currently running, the longest one ever, the average of its longest runs, its draw debt and its rank in the draw-likelihood field. Use it to answer "how often does this team draw?" or "how long since they last drew?".

Takes a numeric id or a slug, whichever you already hold; both come from list_teams.

Free: no key needed, and it costs a key holder nothing either.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamYesNumeric team id or slug — 431 or "arsenal". Find either with list_teams.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "properties": {
+        "country": {
+          "description": "The country a team or competition belongs to.",
+          "properties": {
+            "fifa_code": {
+              "description": "Three-letter FIFA code.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "id": {
+              "type": "integer"
+            },
+            "name": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "id"
+          ],
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "exists_now": {
+          "type": "boolean"
+        },
+        "full_name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "type": "integer"
+        },
+        "name": {
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        },
+        "stats": {
+          "description": "All-time draw statistics.",
+          "properties": {
+            "current_no_draw_streak": {
+              "description": "Matches since the last draw.",
+              "type": [
+                "integer",
+                "null"
+              ]
+            },
+            "draw_debt": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "draw_pct": {
+              "description": "Share of matches drawn, in percent.",
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "draw_rank": {
+              "type": [
+                "integer",
+                "null"
+              ]
+            },
+            "draw_score": {
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "draws": {
+              "type": "integer"
+            },
+            "last_match_date": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "max_no_draw_streak": {
+              "description": "Longest run without a draw, ever.",
+              "type": [
+                "integer",
+                "null"
+              ]
+            },
+            "played": {
+              "type": "integer"
+            }
+          },
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "type": {
+          "description": "\"national_team\" or \"club\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "id",
+        "slug",
+        "name"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark the tool readOnly and idempotent. The description adds useful non-schema context: it is free, requires no key, and costs key holders nothing. It also discloses the scope of returned data beyond a simple profile, such as draw statistics and rankings. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized and front-loaded with the core purpose, followed by return details, usage examples, parameter guidance, and access notes. Some phrasing like 'the numbers this database is built on' is slightly verbose, but every sentence adds useful information.

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?

This is a simple single-parameter lookup tool with complete schema coverage, a readOnly/idempotent annotation pair, and an output schema present. The description covers what the tool does, when to use it, how to pass the parameter, and access/auth implications. Nothing essential is missing.

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?

The schema already thoroughly documents the single 'team' parameter with a concrete example ('431 or "arsenal"') and how to find it. The description adds 'whichever you already hold' and repeats the list_teams source, but provides no meaningful additional semantic detail. Baseline 3 is appropriate.

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 states the tool returns 'One team's profile and its all-time draw statistics' with a specific resource (team) and content focus. It is distinct enough from siblings like get_draw_model or get_team_prediction, though it does not explicitly call out those differences.

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 gives explicit use cases: 'how often does this team draw?' and 'how long since they last drew?'. It also explains how to provide the input via list_teams. It does not name alternative tools or exclusions, but the usage context is clear.

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

All Football Database and Results toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources