Skip to main content
Glama

Football Database and Results

by io.fdb4
OverviewDiscussionsAdmin

Teams most overdue a draw

predict_draws
Read-onlyIdempotent

[PAID] Rank teams by how overdue a draw is — the question this database exists to answer.

Every team has a historical draw rate and a run of matches since its last draw. When the run is long relative to how often that team normally draws, the team is carrying "draw debt", and this tool ranks the whole field by it, most overdue first. Ask it "which national teams are most due a draw?" or "who is overdue a draw in the World Cup 2026 field?" and it answers directly; nothing else here needs to be queried first.

Each entry returns the rank, the score, and the signals behind it: matches played, draws, draw percentage, the current no-draw streak, the longest ever, and the debt figure. Filters subset which teams are listed — a team's score and rank are global and never change with them. Historical pattern, not a betting tip.

Costs 1 point per call (1 point = 1 cent); paginated calls cost 1 point per page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoRestrict the ranking to national teams or to clubs. Omit to rank both together.
limitNoHow many ranked teams to return. Default 25, max 500. One call, one point, whatever the limit.
recentNoOnly teams with a recent match, so the answer is about teams currently playing. Default true.
wc2026NoRestrict to the 2026 World Cup team group. Default false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesTeams ranked by how overdue a draw is, most overdue first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Teams ranked by how overdue a draw is, most overdue first.",
+      "items": {
+        "description": "A ranked team.",
+        "properties": {
+          "last_match_date": {
+            "description": "Date of the team's most recent match.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "rank": {
+            "description": "Position in the ranking; 1 is the most overdue.",
+            "type": "integer"
+          },
+          "score": {
+            "description": "The draw-likelihood score the ranking sorts on.",
+            "type": "number"
+          },
+          "signals": {
+            "description": "The figures the score is built from.",
+            "properties": {
+              "current_no_draw_streak": {
+                "description": "Matches since the last draw.",
+                "type": [
+                  "integer",
+                  "null"
+                ]
+              },
+              "draw_debt": {
+                "description": "Draws expected from the draw rate minus draws that came.",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "draw_pct": {
+                "description": "Share of matches drawn, in percent.",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "draws": {
+                "type": "integer"
+              },
+              "max_no_draw_streak": {
+                "description": "Longest run without a draw, ever.",
+                "type": [
+                  "integer",
+                  "null"
+                ]
+              },
+              "played": {
+                "type": "integer"
+              }
+            },
+            "type": "object"
+          },
+          "team": {
+            "description": "A team.",
+            "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": {
+                "description": "False for a team that no longer exists.",
+                "type": "boolean"
+              },
+              "full_name": {
+                "description": "Official or long name, when known.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "id": {
+                "description": "Team id — the argument every team tool takes.",
+                "type": "integer"
+              },
+              "name": {
+                "description": "Short display name.",
+                "type": "string"
+              },
+              "slug": {
+                "description": "URL slug; accepted anywhere an id is.",
+                "type": "string"
+              },
+              "type": {
+                "description": "\"national_team\" or \"club\".",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "id",
+              "slug",
+              "name"
+            ],
+            "type": "object"
+          }
+        },
+        "required": [
+          "rank",
+          "score"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses the paid cost (1 point per call, per page), the global nature of scores and ranks regardless of filters, the returned signal fields, and the caveat that it is a historical pattern, not a betting tip. This is rich behavioral context that annotations alone do not provide.

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 front-loaded with the core purpose, then builds the concept, examples, return fields, filter caveat, and cost in a logical order. Every sentence earns its place, including the non-betting disclaimer and pagination cost note, with no filler or redundancy.

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?

For a paid read-only tool with an output schema, the description is complete: it explains the ranking logic, what each result contains, how filters behave, cost implications, and example usage. An agent has everything needed to select and invoke this tool correctly without consulting siblings or external docs.

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 the baseline is 3. The description adds meaningful semantics by explaining that filters subset which teams are listed while a team's score and rank remain global and unchanged, which is not obvious from the schema alone. It also reiterates the cost behavior tied to limit/pagination, adding value beyond the parameter descriptions.

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 opens with a specific verb and resource: 'Rank teams by how overdue a draw is' and then explains the draw-debt concept in concrete terms. It is clear and distinct from the title, but it does not explicitly name sibling tools or differentiate itself from them, so it falls just short of the highest bar.

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 example queries ('which national teams are most due a draw?') and states that nothing else needs to be queried first, providing clear context for when to use it. It does not state when not to use it or mention alternatives, so it lacks explicit exclusions.

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