Skip to main content
Glama

Squiggle Teams

squiggle_teams
Read-onlyIdempotent

List all AFL teams tracked by Squiggle, optionally filtered to a specific year; returns team IDs, names, and abbreviations used across other tools.

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

Input Schema

NameRequiredDescriptionDefault
yearNo

Output Schema

NameRequiredDescriptionDefault
teamsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 the useful note that team abbreviations are 'used across other tools' (a real cross-call behavior hint), but restating the return fields is largely duplicative since an output schema exists.

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?

One compact sentence with the action, optional filter, and payload ordering front-loaded. No filler or repetition.

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?

For a zero-required-parameter read tool with full annotation coverage and an output schema, this description covers what it does, what the one parameter means, and what comes back. Only the lack of explicit sibling routing keeps it short of full completeness.

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

Parameters4/5

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

Schema description coverage is 0% for the single `year` parameter, so the description must carry the meaning. It does: it identifies `year` as an optional filter scoping the team list, which is more than the bare `number` type in the schema provides.

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: 'List all AFL teams tracked by Squiggle.' The resource (teams) is clearly distinct from the surrounding squiggle_games/squiggle_sources/squiggle_standings tools, though it never names an alternative explicitly.

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 phrase 'optionally filtered to a specific year' implies when the parameter is useful, but there is no explicit when-to-use vs when-not guidance and no routing to a sibling tool. Adequate but leaves the agent to infer the context.

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.