Skip to main content
Glama

Squiggle Games

squiggle_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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": 2024,
      "round": 1
    },
    "name": "squiggle_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo
roundNo
completeNoFilter to completed games.

Output Schema

NameRequiredDescriptionDefault
gamesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the description only needs to add scoping context. It identifies the upstream source (Squiggle) and the returned fields, but says nothing about what happens with zero filters, result volume, or any upstream rate limits/availability caveats for a tool where all three parameters are optional.

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 source and filters first, then the payload. The return-field list partially duplicates the existing output schema, which is the only wasteful element.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values are adequately covered even without the description's field list. However, with three optional parameters at 33% schema coverage, the definition never states the no-filter default behavior, which is the main ambiguity an agent would face when calling it.

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 only 33% — just 'complete' is documented — so the description carries extra burden and does add that year, round, and completion status are combinable ('and/or'). It still does not clarify accepted year format, whether round is a number or a name, or the default scope when no filters are supplied.

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?

States a specific verb and resource ('Fetch AFL fixture and results from Squiggle') plus the filtering dimensions, so an agent knows exactly what data comes back. It does not distinguish itself from siblings such as squiggle_standings or squiggle_teams, leaving that differentiation to inference.

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?

Usage is implied by the filter list ('filtered by year, round, and/or completion status'), which suggests querying a season, a round, or only finished games. There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives for standings or team data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.