Squiggle

Games

games

Read-onlyIdempotent

Fetch AFL fixture and results from Squiggle, filtered by year, round, and/or completion status; returns scores, venues, dates, and match IDs.

Input Schema

Name	Required	Description
`year`	No
`round`	No
`complete`	No	Filter to completed games.

Output Schema

Name	Required	Description	Default
`games`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 16, 2026

removedOutput schema / properties / count

Removed value: -{
-  "description": "Number of items returned.",
-  "type": "integer"
-}

addedOutput schema / properties / games

Added value: +{
+  "items": {
+    "properties": {
+      "abehinds": {
+        "type": "number"
+      },
+      "agoals": {
+        "type": "number"
+      },
+      "ascore": {
+        "type": "number"
+      },
+      "ateam": {
+        "type": "string"
+      },
+      "ateamid": {
+        "type": "number"
+      },
+      "complete": {
+        "type": "number"
+      },
+      "date": {
+        "type": "string"
+      },
+      "hbehinds": {
+        "type": "number"
+      },
+      "hgoals": {
+        "type": "number"
+      },
+      "hscore": {
+        "type": "number"
+      },
+      "hteam": {
+        "type": "string"
+      },
+      "hteamid": {
+        "type": "number"
+      },
+      "id": {
+        "type": "number"
+      },
+      "is_final": {
+        "type": "number"
+      },
+      "is_grand_final": {
+        "type": "number"
+      },
+      "localtime": {
+        "type": "string"
+      },
+      "round": {
+        "type": "number"
+      },
+      "roundname": {
+        "type": "string"
+      },
+      "timestr": {
+        "type": "string"
+      },
+      "tz": {
+        "type": "string"
+      },
+      "unixtime": {
+        "type": "number"
+      },
+      "updated": {
+        "type": "string"
+      },
+      "venue": {
+        "type": "string"
+      },
+      "winner": {
+        "type": "string"
+      },
+      "winnerteamid": {
+        "type": "number"
+      },
+      "year": {
+        "type": "number"
+      }
+    },
+    "type": [
+      "object",
+      null
+    ]
+  },
+  "type": "array"
+}

removedOutput schema / properties / items

Removed value: -{
-  "items": {
-    "properties": {
-      "away_score": {
-        "description": "Away team score",
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "away_team": {
-        "description": "Away team name",
-        "type": "string"
-      },
-      "complete": {
-        "description": "Whether game is completed",
-        "type": "boolean"
-      },
-      "date": {
-        "description": "Game date and time",
-        "type": "string"
-      },
-      "home_score": {
-        "description": "Home team score",
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "home_team": {
-        "description": "Home team name",
-        "type": "string"
-      },
-      "id": {
-        "description": "Game ID",
-        "type": "number"
-      },
-      "round": {
-        "description": "Round number",
-        "type": "number"
-      },
-      "year": {
-        "description": "Season year",
-        "type": "number"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / required

Removed value: -[
-  "items",
-  "count"
-]

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "round": 1,
+    "year": 2024
+  },
+  {
+    "complete": true,
+    "round": 5,
+    "year": 2024
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "away_score": {
+            "description": "Away team score",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "away_team": {
+            "description": "Away team name",
+            "type": "string"
+          },
+          "complete": {
+            "description": "Whether game is completed",
+            "type": "boolean"
+          },
+          "date": {
+            "description": "Game date and time",
+            "type": "string"
+          },
+          "home_score": {
+            "description": "Home team score",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "home_team": {
+            "description": "Home team name",
+            "type": "string"
+          },
+          "id": {
+            "description": "Game ID",
+            "type": "number"
+          },
+          "round": {
+            "description": "Round number",
+            "type": "number"
+          },
+          "year": {
+            "description": "Season year",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}

First observedMay 14, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds only that matches are sourced from Squiggle and lists returned fields; it says nothing about rate limits, data freshness, or behavior on an empty filter.

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?

A single front-loaded sentence with the verb first, then source, filters, and return fields. Nothing is wasted, though the semicolon-clause of return values is dense and slightly redundant given the output schema exists.

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 present, the description need not explain return shape, and annotations cover safety. Purpose, source, and filter dimensions are all present for a 3-parameter, no-required-parameter tool, so the definition is essentially complete for correct invocation.

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 coverage is 33%, with only 'complete' documented in the schema. The description compensates partially by naming all three filter dimensions and noting they can be combined ('and/or'), but it adds no format or semantics for 'year' and 'round' (e.g. valid ranges, whether round is numeric-only), leaving the coverage gap only half-closed.

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 a specific verb and resource ('Fetch AFL fixture and results'), names the data source (Squiggle), and enumerates the filter dimensions. This clearly separates it from siblings like teams and standings, which expose different resources from the same domain.

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 implies usage via 'filtered by year, round, and/or completion status,' signalling how to scope the query. It never states when to prefer this over siblings such as standings or teams, so the agent must infer the boundary itself.

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

All Squiggle 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.