Skip to main content
Glama

Squiggle Standings

squiggle_standings
Read-onlyIdempotent

Fetch the AFL ladder (standings) for a given year and optional round from Squiggle; returns wins, losses, points, and percentage for each team.

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": 10
    },
    "name": "squiggle_standings"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo
roundNo

Output Schema

NameRequiredDescriptionDefault
standingsNo

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 readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is fully covered and the description need not repeat it. What the description adds — the metrics returned (wins, losses, points, percentage) — duplicates the output schema rather than contributing behavioral context such as data freshness or defaults for missing parameters.

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?

A single front-loaded sentence with the source and scope established before the return details. No filler, no redundancy in phrasing.

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 annotations covering safety and an output schema covering return shape, the remaining burden is light and the description meets most of it by naming the source, scope, and metric set. The one real omission is defaulting behavior when the optional year and round are not supplied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and neither parameter carries a description, so the description bears the full burden. It only restates that year is the season and round is optional, without specifying accepted formats, ranges, or the default season when year is omitted — a gap given both parameters are optional.

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 (fetch), resource (AFL ladder/standings), source (Squiggle), and scope (year plus optional round), so an agent knows exactly what it retrieves. It does not differentiate itself from the similarly-named 'ladder' sibling, leaving the choice between them 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?

The description implies usage by naming the required input (year) and the optional one (round), which hints at when the tool applies. It offers no explicit when-to-use versus alternatives, no exclusions, and no note on what happens when year or round is omitted.

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.