Skip to main content
Glama

Squiggle Sources

squiggle_sources
Read-onlyIdempotent

List all registered AFL tipping sources in Squiggle (models, pundits, bookmakers) with their numeric IDs; use IDs with tips and ladder.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
sourcesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile needs no restating. The description adds genuinely new behavior: the response is a registry of named sources with numeric IDs, and those IDs are the keys consumed by other tools — useful data-flow context. It does not mention whether the list is season-scoped or how large it typically is.

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 sentence with two clauses: the first states what is listed and what is returned, the second states how the output is used. Nothing is wasted and the most decision-relevant information leads.

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, return-value details need no prose, and the description correctly focuses on purpose and downstream usage. The only minor gap is scope — whether the registry is static across seasons or varies — but for a zero-parameter lookup this is close to complete.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. The schema's empty property set is consistent with a pure enumeration call.

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?

Uses a specific verb and resource ('List all registered AFL tipping sources in Squiggle') and immediately clarifies what a source is (models, pundits, bookmakers) plus what it returns (numeric IDs). This distinguishes it cleanly from the data-bearing siblings `tips` and `ladder`.

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

Usage Guidelines4/5

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

The clause 'use IDs with `tips` and `ladder`' explicitly routes the agent: call this first to obtain an ID, then pass it to those tools. It stops short of stating exclusions (e.g. that this tool returns no tipping data itself), so it is clear but not fully exhaustive.

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.