Football Database and Results

Find a team

list_teams

Read-onlyIdempotent

[FREE] Find a team and its id — the lookup every other team tool depends on.

Search by name prefix with q ("arse" finds Arsenal), or browse by first letter, or list one kind of team. Each row carries the numeric id and the slug that get_team, get_team_streaks, get_team_prediction, head_to_head and search_results take.

The database holds thousands of teams, so an unfiltered call returns the first 25 with the full total beside them. Always pass q when you know the name.

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

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Name prefix, matched against both the short and the full name. The fastest way to find one team.
`type`	No	Restrict to national teams or to clubs.
`limit`	No	How many teams to return. Default 25; the total number of matches is always reported.
`letter`	No	First letter A-Z to browse by, or "#" for names starting with a non-letter.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Teams matching the search.
`hint`	No	Present only when rows were left out: how to narrow the call.
`total`	Yes	How many rows matched before the limit.
`returned`	Yes	How many rows are in data.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Teams matching the search.",
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "hint": {
+      "description": "Present only when rows were left out: how to narrow the call.",
+      "type": "string"
+    },
+    "returned": {
+      "description": "How many rows are in data.",
+      "type": "integer"
+    },
+    "total": {
+      "description": "How many rows matched before the limit.",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "data",
+    "total",
+    "returned"
+  ],
+  "type": "object"
+}

First observedSep 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already mark this as read-only and idempotent. The description adds useful behavioral context beyond that: unfiltered calls return only the first 25 with a total count, rows carry the id and slug, and the tool is free with no key needed. This is meaningful additional transparency without contradicting the 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 front-loaded with the core purpose and immediately gives a concrete example. It is mostly efficient, though the free/no-key point is stated twice, adding mild redundancy. Overall it earns its length with useful routing and behavioral details.

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 lookup tool with a rich input schema and an output schema present, the description covers what an agent needs: how to search, what each result row contains, the default limit behavior, and the relationship to downstream team tools. No critical invocation information 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?

Schema description coverage is 100%, so the schema already documents all four parameters clearly. The description adds a helpful example ('arse' finds Arsenal) and notes the default limit behavior, but these are marginal enrichments over the schema rather than necessary compensations.

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 states a specific verb and resource: 'Find a team and its id'. It also explicitly positions itself as 'the lookup every other team tool depends on', which clearly distinguishes it from the sibling team tools like get_team and head_to_head.

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 clear usage context: search by prefix with q, browse by first letter, or filter by team type. It also gives an explicit rule—'Always pass q when you know the name'—which is actionable. It does not explicitly name alternatives or state when not to use this tool, but the role as a dependency lookup makes the intended use 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 tools Inspect

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

Need Help?