Skip to main content
Glama

Prediction Market Rule Check MCP

doubles_today

PAID $1.00/call (x402 USDC on Base; one call returns the whole day's picks, so $1 a day) or the $15/month doubles plan. Not included in the £12/month plan, bundle passes or trial keys. Sports doubles feed (info only, 18+): today's stats-led doubles from Grok Double Bot with legs, kick-off/start times (UK), odds at tip time, combined odds, confidence and rationale. Information only, not betting advice. No guaranteed returns. 18+. BeGambleAware.org

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "doubles_today"
  }
}

Input Schema

NameRequiredDescriptionDefault
access_tokenNo$15/month doubles plan token from /success (or Authorization: Bearer)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / access_token / description
      Previous value: -"Subscriber token from /success (or Authorization: Bearer)"New value: +"$15/month doubles plan token from /success (or Authorization: Bearer)"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the paid access model ($1.00/call via x402 USDC on Base, or $15/month token), that one call returns the entire day's picks, and that trial keys/bundles/£12 plan are not valid. It omits what happens when access fails and any rate or error behavior.

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?

Front-loads the payment gating, then the resource and returned fields, then disclaimers — a sensible ordering for a paid tool. It is dense but each clause carries real information; the repeated disclaimers ("Information only", "18+" twice) are the only mild redundancy.

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?

No output schema exists, so the description properly enumerates the returned fields instead of leaving them unknown, and it covers the material prerequisite (paid token). It stops short of explaining failure modes or the geographic/jurisdictional limits implied by the UK-time and 18+ notes.

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

Parameters3/5

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

Schema coverage is 100% and the single access_token parameter is fully documented in the schema, including the /success origin and Bearer alternative. The description adds plan context ($15/month doubles plan) but no new syntax or format detail, so baseline 3 applies.

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 resource and scope: "today's stats-led doubles from Grok Double Bot," with a concrete enumeration of returned fields (legs, kick-off times, odds, combined odds, confidence, rationale). The word "today" implicitly separates it from the historical sibling doubles_record, though that sibling is never named.

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?

Usage context is implied by the feed's "today" framing and the pricing/plan gating, but there is no explicit when-to-use versus when-not guidance and no pointer to doubles_record for historical picks or to other siblings. The agent must infer that this is the daily-picks tool rather than the archive.

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.