Skip to main content
Glama

Squiggle

by io.github.pipeworx-io

Tips

tips
Read-onlyIdempotent

Tips per game per source.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNo
roundNo
sourceNoSource id (from /sources).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tipsNo

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": {
-      "confidence": {
-        "description": "Confidence percentage",
-        "type": "number"
-      },
-      "game_id": {
-        "description": "Game ID",
-        "type": "number"
-      },
-      "source_id": {
-        "description": "Source ID",
-        "type": "number"
-      },
-      "tip": {
-        "description": "Team tipped to win",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / tips
      Added value: +{
+  "items": {
+    "properties": {
+      "ateam": {
+        "type": "string"
+      },
+      "ateamid": {
+        "type": "number"
+      },
+      "bits": {
+        "type": "string"
+      },
+      "confidence": {
+        "type": "string"
+      },
+      "correct": {
+        "type": "number"
+      },
+      "date": {
+        "type": "string"
+      },
+      "err": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "gameid": {
+        "type": "number"
+      },
+      "hconfidence": {
+        "type": "string"
+      },
+      "hmargin": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "hteam": {
+        "type": "string"
+      },
+      "hteamid": {
+        "type": "number"
+      },
+      "margin": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "round": {
+        "type": "number"
+      },
+      "source": {
+        "type": "string"
+      },
+      "sourceid": {
+        "type": "number"
+      },
+      "tip": {
+        "type": "string"
+      },
+      "tipteamid": {
+        "type": "number"
+      },
+      "updated": {
+        "type": "string"
+      },
+      "venue": {
+        "type": "string"
+      },
+      "year": {
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / required
      Removed value: -[
-  "items",
-  "count"
-]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "round": 3,
+    "source": 1,
+    "year": 2024
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "confidence": {
+            "description": "Confidence percentage",
+            "type": "number"
+          },
+          "game_id": {
+            "description": "Game ID",
+            "type": "number"
+          },
+          "source_id": {
+            "description": "Source ID",
+            "type": "number"
+          },
+          "tip": {
+            "description": "Team tipped to win",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds no extra behavioral context such as data source or limitations, but it does not contradict the annotations. With the annotations carrying most of the burden, a 3 is appropriate.

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 extremely concise—a single sentence with no filler. It front-loads the key information without waste, making it easy to parse.

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

Completeness2/5

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

Despite having output schema and annotations, the description is too sparse to be complete. It leaves unclear what the output structure is (though schema covers it) and does not explain the meaning of 'year' and 'round' parameters. More detail is needed for full contextual understanding.

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 only 33% (only 'source' is described). The description 'per game per source' hints that 'year' and 'round' help identify games, but it does not explain the format or allowed values for these parameters, so it only partially compensates for the low schema coverage.

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?

The description 'Tips per game per source' clearly identifies the resource (tips) and the scope (per game per source), making the tool's purpose understandable. However, it lacks a verb and does not differentiate this tool from siblings like 'games' or 'sources', so it falls short of a 5.

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?

There is no guidance on when to use this tool versus alternatives. The description merely states what the tool returns without any context about scenarios, prerequisites, or exclusions, leaving the agent without direction on tool selection.

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