Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

squiggle: Get games

squiggle_get_games
Read-onlyIdempotent

Fetch AFL games and filter by team, season, round, or completion status; returns teams, scores, venue, and time.

Instructions

Get AFL games with optional filters. Returns home/away teams, scores, completion status, venue, and time.

Input Schema

NameRequiredDescriptionDefault
teamNoTeam id (use squiggle_get_teams to list)
yearNoSeason year (e.g. 2024)
roundNoRound number
fieldsNoKeys to keep (comma-separated).
completeNoCompletion % filter (100 = finished games only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Keys to keep (comma-separated).",
+  "type": "string"
+}
    • removedInput schema / properties / round / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / team / maximum
      Removed value: -9007199254740991
  2. Changed3 schema fields changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / round / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / team / maximum
      Added value: +9007199254740991
  3. First observedv1.2.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds only that results are filterable and lists returned fields; it says nothing about pagination, default season behavior when no year is given, or result limits. With annotations carrying safety, the extra value is thin.

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?

Two tight sentences with no waste; the filter hint and the field list are front-loaded and immediately scannable.

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?

Adequate but not complete: no output schema exists, yet the description does mention returned fields (teams, scores, completion status, venue, time), which partially compensates. However it omits default behavior for omitted filters (e.g., all seasons) and any ordering/pagination details.

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 100%, so each parameter is already documented (team id, year range, round, fields keys, completion %). The description only gestures at 'optional filters' without adding format or behavior details beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 (Get) and resource (AFL games), and enumerates returned fields. It's clear on its own, though it doesn't distinguish itself from squiggle siblings like squiggle_get_ladder or squiggle_get_tips, which is minor given the game-vs-ladder distinction is obvious.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Mentions 'optional filters' but gives no guidance on when to use this tool versus siblings such as squiggle_get_ladder, squiggle_get_standings, or the many other league game-fetching tools (mlb_get_schedule, nhl_get_schedule, euroleague_get_games). No when-to-use or exclusions.

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

Deploy Server

Other Tools