Skip to main content
Glama

Squiggle

by io.github.pipeworx-io

Sources

sources
Read-onlyIdempotent

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourcesNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / count
      Removed value: -{
-  "description": "Number of items returned.",
-  "type": "integer"
-}
    • removedOutput schema / properties / items
      Removed value: -{
-  "items": {
-    "properties": {
-      "id": {
-        "description": "Source ID",
-        "type": "number"
-      },
-      "long_name": {
-        "description": "Full source name",
-        "type": "string"
-      },
-      "name": {
-        "description": "Source name",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / sources
      Added value: +{
+  "items": {
+    "properties": {
+      "icon": {
+        "type": "string"
+      },
+      "id": {
+        "type": "number"
+      },
+      "name": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / required
      Removed value: -[
-  "items",
-  "count"
-]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Source ID",
+            "type": "number"
+          },
+          "long_name": {
+            "description": "Full source name",
+            "type": "string"
+          },
+          "name": {
+            "description": "Source name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds useful context by specifying the domain (AFL tipping) and the scope (all registered sources), which complements rather than repeats annotations. No contradictions.

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?

The description is a single well-structured sentence with a semicolon separating the primary action from usage guidance. Every phrase contributes value, with no filler or redundancy.

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

Completeness5/5

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

Given the tool's simplicity (no parameters, output schema present), the description provides everything needed for selection and integration. It states what is listed, the categories of sources, and how to use the output with related tools, making it complete for its scope.

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 has zero parameters, so the baseline is 4. The description adds no parameter-specific information, but none is needed since the schema is empty. It does convey what the result contains (numeric IDs), which is the relevant semantic here.

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?

The description clearly states the tool lists all registered AFL tipping sources (models, pundits, bookmakers) with numeric IDs. It differentiates from sibling tools like `tips` and `ladder` by explicitly framing itself as the source of IDs for those tools, making its unique role obvious.

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 description gives clear context: use this tool to obtain numeric IDs for use with `tips` and `ladder`. It doesn't explicitly exclude other tools, but for a simple list tool with no parameters, the guidance is sufficient and direct.

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

All Squiggle toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation2/5

Several tools occupy overlapping boundaries: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicate query entry points (beta is currently identical), while ladder/standings, ai_visibility_check/scan_competitor_ai_presence, and polymarket_edges/polymarket_arbitrage also blur together. An agent would struggle to reliably pick the right tool without reading very long descriptions.

Naming Consistency4/5

The vast majority of names are snake_case and many follow a readable verb_noun shape, such as resolve_entity, validate_claim, and list_subscriptions. However, the Squiggle/AFL tools are bare nouns (games, ladder, sources, standings, teams, tips), and the polymarket_* / pipeworx_* prefixes do not use one consistent verb style, so it is not a fully uniform convention.

Tool Count2/5

37 tools is in the too-many band, and the sprawl is compounded by mixing unrelated domains under one server: AFL stats, a huge Pipeworx data-routing layer, prediction-market analytics, AI visibility checks, npm dependency review, and llms.txt generation. The set feels like several merged servers rather than one well-scoped MCP.

Completeness3/5

The query/research surface is broad and covers many subdomains, and the subscription lifecycle is reasonably complete with subscribe/list/unsubscribe/recent_alerts. However, pipeworx:// citation URIs are prominently returned but no tool fetches a cited record directly, the AFL side lacks player-level data, and subscriptions cannot be updated.

Resources