Skip to main content
Glama

Prediction Market Rule Check MCP

doubles_record

FREE. Sports doubles feed (info only, 18+): the full SETTLED record of Grok Double Bot's daily doubles, every pick including losses, with legs, odds at tip time and result; won/lost/void counts, win rate, average combined odds and running profit on a flat £10 stake, plus pre-kickoff SHA-256 fingerprints of each day's sealed picks (salt + text revealed after they settle; public page /record). Never shows unsettled picks. 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_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost recent N settled picks to list (1-500, default all up to 500). Stats always cover the full record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 behavioral burden and mostly succeeds: it discloses that losses are included (no cherry-picking), that picks are sealed pre-kickoff and verified by SHA-256 fingerprint with salt and text revealed after settlement, that the record is settled-only, and that stats are computed on a flat £10 stake. It does not state read-only-ness or rate limits, but as an informational public feed that gap is minor.

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

Conciseness3/5

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

The description is front-loaded well ('FREE', then what the tool returns), but roughly a third of it is legal boilerplate: 'Information only, not betting advice. No guaranteed returns. 18+. BeGambleAware.org' repeats the same compliance point three times. Those sentences crowd out more useful routing information.

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?

There is no output schema, so the description must explain the return shape, and it does list the returned fields in detail: legs, odds at tip time, result, won/lost/void counts, win rate, average combined odds, running profit and fingerprint data. For a single optional-parameter read tool, that is close to complete, with only the sibling routing left implicit.

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 description coverage is 100%, so the single limit parameter is already fully documented, including the default and range, and its note that stats always cover the full record. The description adds no syntax or format detail beyond the schema, so the baseline of 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?

The description names a specific resource and scope: the full SETTLED record of Grok Double Bot's daily doubles, with every pick including losses. The emphasis on 'SETTLED' and 'never shows unsettled picks' implicitly separates it from the sibling doubles_today, but the sibling is never named, so an agent must infer the boundary.

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 is implied rather than stated: 'NEVER shows unsettled picks' tells the agent to look elsewhere for pending picks, but no sibling (doubles_today) is named and no explicit when-to-use or when-not-to-use rule is given. An agent can infer the routing, but it has to do the work.

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.