Skip to main content
Glama
jarvismaximum-hue

ProfitPlay MCP Server

bet

Place bets on prediction markets for cryptocurrency and stock price movements. Specify game type, direction (UP/DOWN), probability price, and share quantity to execute trades.

Instructions

Place a bet on a prediction market. Cost = shares * price.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameTypeYesGame type, e.g. 'btc-5min'
sideYesPredict UP or DOWN
priceYesProbability price 0.01-0.99 (0.5 = even odds)
sharesYesNumber of shares to buy

Implementation Reference

  • The handler logic for the 'bet' tool, which performs an API POST request to place a bet.
    case "bet":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              await apiPost(`/api/games/${args?.gameType}/bet`, {
                side: args?.side,
                price: args?.price,
                shares: args?.shares,
              }),
              null,
              2,
            ),
          },
        ],
      };
  • The schema definition for the 'bet' tool, specifying input parameters and descriptions.
    {
      name: "bet",
      description: "Place a bet on a prediction market. Cost = shares * price.",
      inputSchema: {
        type: "object" as const,
        properties: {
          gameType: { type: "string", description: "Game type, e.g. 'btc-5min'" },
          side: { type: "string", enum: ["UP", "DOWN"], description: "Predict UP or DOWN" },
          price: { type: "number", description: "Probability price 0.01-0.99 (0.5 = even odds)" },
          shares: { type: "number", description: "Number of shares to buy" },
        },
        required: ["gameType", "side", "price", "shares"],
      },
    },
Behavior3/5

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

No annotations provided, so description carries full burden. Adds useful cost calculation formula (shares * price) indicating financial commitment, but omits return value structure, error conditions (e.g., insufficient funds), idempotency, or whether bets can be cancelled via the 'cancel' sibling.

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?

Two sentences total with zero waste: first establishes purpose, second provides critical cost information. Efficiently front-loaded and appropriately sized for the parameter complexity.

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

Completeness3/5

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

With 4 simple parameters and 100% schema coverage, the description covers basics adequately. However, for a financial mutation tool with no output schema, it lacks explanation of return values (e.g., bet ID, confirmation), success/failure signals, or post-bet state changes.

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 coverage is 100%, establishing baseline 3. Description adds valuable semantic relationship between 'price' and 'shares' via the cost formula, helping users understand how parameters interact to determine financial outlay.

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?

Clear verb 'Place' and resource 'bet' with domain 'prediction market' specified. However, does not explicitly differentiate from sibling tools like 'arena' or 'market' that might overlap conceptually.

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?

No guidance provided on when to use this tool versus alternatives like 'arena' or 'cancel', nor any prerequisites (e.g., registration, balance requirements) mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jarvismaximum-hue/profitplay-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server