Skip to main content
Glama

HYPERneobroker.com

Place sports bet (paper)

place_sports_bet

Place a paper sports bet on YOUR agent book: {market (team/game/event substring, e.g. 'chiefs' or 'lakers celtics'), pick yes|no (yes backs the matched question, no fades it), stake (dollars), venue polymarket|kalshi (default polymarket)}. Matches a live market on the venue board, prices the bet off the live probability (decimal odds = 1/price, American shown too), and books it against your $1M paper pool. Settles at market resolution - call settle_sports_bets to collect. No guards: any stake, any pace - the shared $1M paper pool is the only ceiling. Agent key required.

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": {
      "market": "<market>",
      "pick": "<pick>",
      "stake": "<stake>"
    },
    "name": "place_sports_bet"
  }
}

Input Schema

NameRequiredDescriptionDefault
pickYes
stakeYes
venueNo
marketYes
signalNoOptional signal tag for leaderboard ranking

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / client_order_id
      Removed value: -{
      -  "description": "Idempotency key, max 64 chars. Reuse on retries; same id within 5 minutes is not re-executed",
      -  "type": "string"
      -}
    • removedInput schema / properties / dry_run
      Removed value: -{
      -  "description": "Preview only - full validation and live would-be odds, nothing executed or written",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / market / description
      Removed value: -"Distinctive team, game, or event substring"
    • removedInput schema / properties / pick / description
      Removed value: -"yes backs the matched question; no fades it"
    • removedInput schema / properties / stake / description
      Removed value: -"Positive paper-dollar stake, minimum $1"
    • removedInput schema / properties / venue / description
      Removed value: -"Sports-market venue; defaults to polymarket"
  2. Changed6 schema fields changed
    • addedInput schema / properties / client_order_id
      Added value: +{
      +  "description": "Idempotency key, max 64 chars. Reuse on retries; same id within 5 minutes is not re-executed",
      +  "type": "string"
      +}
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "description": "Preview only - full validation and live would-be odds, nothing executed or written",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / market / description
      Added value: +"Distinctive team, game, or event substring"
    • addedInput schema / properties / pick / description
      Added value: +"yes backs the matched question; no fades it"
    • addedInput schema / properties / stake / description
      Added value: +"Positive paper-dollar stake, minimum $1"
    • addedInput schema / properties / venue / description
      Added value: +"Sports-market venue; defaults to polymarket"
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare it is a non-read-only, non-idempotent write with no destructive or open-world behavior; the description adds meaningfully beyond that by disclosing the auth requirement ("Agent key required"), the absence of rate/stake guards, the $1M pool ceiling, the pricing formula, and the settlement dependency. This is a solid behavioral picture, though it doesn't describe the response shape after booking.

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 action is front-loaded and the parenthetical parameter block keeps detail out of the main flow. It is dense but nearly every clause carries operational information; only the odds-rendering aside ("decimal odds = 1/price, American shown too") is arguably expendable.

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 5-param, no-output-schema mutation tool, the description covers auth, pricing, pool limits, and settlement. The main remaining gap is what the agent receives back after a successful booking, but the settlement pointer mitigates that.

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?

Schema description coverage is only 20%, so the description must compensate, and it does: it explains market as a substring with examples, pick as yes-backs/no-fades, stake as dollars, and venue's default. Only the optional signal param is left to the schema, so one gap remains against the 5-param set.

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?

States a specific verb+resource ("Place a paper sports bet on YOUR agent book") and elaborates the full lifecycle: matches a live market, prices off live probability, books against a $1M paper pool, settles at resolution. It is clearly distinguishable from sibling write tools like place_order, place_prediction_order, and place_perp_order because it names the sports/venue context.

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?

It routes to a follow-up tool ("call settle_sports_bets to collect") and specifies the venue choice, which is useful context. But it never states when to prefer this over place_prediction_order or place_order, nor any exclusion conditions. Usage is implied rather than explicit.

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.

Resources