Skip to main content
Glama
Sign In

BetSlip Doctor

by ai.betslipdoctor
OverviewDiscussionsAdmin

Leagues and teams

onboarding_preferences
Idempotent

Read the current league catalog and per-league team membership, or read/save your leagues and teams. Use original source-qualified IDs. Logos are unavailable. Get the current revision before a confirmed set: merge imports device selections with account order first; replace saves Settings selections and allows clearing. Reuse a stable commandKey for retries. This changes preferences only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "onboarding_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
actionYes
leagueNo
confirmedNo
commandKeyNo
selectionsNo
expectedRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / league / anyOf
      Added value: +[
+  {
+    "pattern": "^(?:LGUE_(?!oa[0-9])|SPRT_)[A-Za-z0-9_-]{1,123}$",
+    "type": "string"
+  },
+  {
+    "pattern": "^LGUE_oa1-[A-Za-z0-9_-]{1,119}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / league / pattern
      Removed value: -"^LGUE_(?!oa[0-9])[A-Za-z0-9_-]{1,123}$"
    • removedInput schema / properties / league / type
      Removed value: -"string"
    • removedInput schema / properties / selections / properties / leagues / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / selections / properties / leagues / items / oneOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "pattern": "^(?:LGUE_(?!oa[0-9])|SPRT_)[A-Za-z0-9_-]{1,123}$",
+        "type": "string"
+      },
+      "source": {
+        "const": "feed_a",
+        "type": "string"
+      }
+    },
+    "required": [
+      "source",
+      "id"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "pattern": "^LGUE_oa1-[A-Za-z0-9_-]{1,119}$",
+        "type": "string"
+      },
+      "source": {
+        "const": "feed_b",
+        "type": "string"
+      }
+    },
+    "required": [
+      "source",
+      "id"
+    ],
+    "type": "object"
+  }
+]
    • removedInput schema / properties / selections / properties / leagues / items / properties
      Removed value: -{
-  "id": {
-    "pattern": "^LGUE_(?!oa[0-9])[A-Za-z0-9_-]{1,123}$",
-    "type": "string"
-  },
-  "source": {
-    "const": "feed_a",
-    "type": "string"
-  }
-}
    • removedInput schema / properties / selections / properties / leagues / items / required
      Removed value: -[
-  "source",
-  "id"
-]
    • removedInput schema / properties / selections / properties / leagues / items / type
      Removed value: -"object"
    • changedInput schema / properties / selections / properties / teams / items / properties / leagueId / pattern
      Previous value: -"^LGUE_(?!oa[0-9])[A-Za-z0-9_-]{1,123}$"New value: +"^(?:LGUE_(?!oa[0-9])|SPRT_)[A-Za-z0-9_-]{1,123}$"
  2. Changed2 schema fields changed
    • changedInput schema / properties / selections / properties / leagues / items / properties / source / const
      Previous value: -"sharpsports"New value: +"feed_a"
    • changedInput schema / properties / selections / properties / teams / items / properties / source / const
      Previous value: -"sharpsports"New value: +"feed_a"
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a non-destructive, idempotent, non-open-world mutation, and the description adds meaningful context beyond them: it changes preferences only, replace can clear selections, logos are unavailable, and retries should reuse a commandKey. The confirmation and revision workflow is also disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but front-loaded and every sentence carries operational information. Some phrases are telegraphic and require decoding, but there is little wasted text for a seven-parameter nested tool.

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 complex mutation tool with nested objects and no output schema, the description covers the critical prerequisites, identity format, mode behavior, and retry semantics. It leaves some return-shape and action-specific details to the schema, but the definition is largely complete for correct invocation.

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?

Despite 0% schema description coverage, the description compensates well by explaining source-qualified IDs, the need for a current revision before confirmed sets, the merge/replace mode semantics, and the purpose of commandKey retries. It does not map every parameter name or nested array limit, but the operational meaning is substantially enriched.

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 names distinct operations: reading the league catalog, reading per-league team membership, and reading/saving the user's leagues and teams. The verbs and resources are specific enough to distinguish the four action modes, though the mapping to the action enum is implied rather than explicit.

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?

It explains when to use merge versus replace ('merge imports device selections with account order first; replace saves Settings selections and allows clearing') and gives prerequisites such as getting the current revision before a confirmed set and reusing a stable commandKey for retries. It does not explicitly say when not to use the tool, but no sibling appears to overlap.

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

All BetSlip Doctor toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources