Skip to main content
Glama

Football Data

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Team

get_team
Read-onlyIdempotent

Team detail by ID — current squad, coach, competitions, venue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
team_idYesfootball-data.org numeric team ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTeam ID
tlaNoThree-letter acronym
nameYesTeam full name
coachNoCoach name
crestNoTeam crest/logo URL
squadYes
venueNoStadium/venue name
colorsNoClub colors description
addressNoTeam address
countryNoCountry name
foundedNoYear founded
websiteNoOfficial website URL
short_nameNoTeam short name
coach_nationalityNoCoach nationality
running_competitionsYesList of competition names team is currently in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "team_id": 64
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "address": {
+      "description": "Team address",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "coach": {
+      "description": "Coach name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "coach_nationality": {
+      "description": "Coach nationality",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "colors": {
+      "description": "Club colors description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "country": {
+      "description": "Country name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "crest": {
+      "description": "Team crest/logo URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "founded": {
+      "description": "Year founded",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Team ID",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "name": {
+      "description": "Team full name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "running_competitions": {
+      "description": "List of competition names team is currently in",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "short_name": {
+      "description": "Team short name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "squad": {
+      "items": {
+        "properties": {
+          "dob": {
+            "description": "Date of birth (YYYY-MM-DD)",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Player ID",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Player name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "nationality": {
+            "description": "Player nationality",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "position": {
+            "description": "Player position",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "tla": {
+      "description": "Three-letter acronym",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "venue": {
+      "description": "Stadium/venue name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "website": {
+      "description": "Official website URL",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "squad",
+    "running_competitions"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, non-destructive behavior. The description adds specific detail about what data is returned (squad, coach, competitions, venue), providing useful context beyond annotations.

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 a single, concise sentence that effectively front-loads the purpose and key return fields. No extraneous content.

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 presence of an output schema, the description adequately covers the tool's behavior. It states what the tool does and what information it retrieves, which is sufficient for a simple read operation.

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 input schema has 100% coverage with a description for team_id. The description does not add further parameter guidance, so baseline 3 is appropriate.

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 clearly states it retrieves team details by ID, listing specific fields (squad, coach, competitions, venue). This distinguishes it from sibling tools like get_team_matches, which focus on match data.

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 does not explicitly state when to use this tool over alternatives or provide use cases. The purpose is implied by the tool name and description, but no direct guidance is given.

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

All Football Data 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