Skip to main content
Glama
Sign In
StreamElements MCP Server

StreamElements MCP Server

by jogalleciez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Place contest bet

contests_bet

Place a bet on a StreamElements contest option as the token owner by providing contest ID, option ID, and point amount.

Instructions

Place a bet on a contest option as the token owner.

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": {
      "contestId": "<contestId>",
      "optionID": "<optionID>",
      "amount": "<amount>"
    },
    "name": "contests_bet"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesPoints to bet
channelNoStreamElements channel id (24-char hex). Defaults to SE_CHANNEL_ID or the channel that owns the token.
optionIDYesOption id (the option's _id from contests_get) (24-character hex id)
contestIdYesContest id (24-character hex id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world mutation. The description adds the 'as the token owner' identity context but does not explain what gets deducted, what failure conditions exist, or whether the contest must be in a specific state. It adds some value beyond the annotations but not rich behavioral detail.

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?

A single front-loaded sentence with no wasted words. The action, target, and actor are all conveyed immediately, and nothing is padded or repeated.

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?

The schema is rich, annotations cover the safety profile, and no output schema exists, so return values need not be explained. However, for a betting mutation, the description omits relevant context like contest state requirements or what happens to the bettor's points, leaving it minimally adequate rather than fully complete.

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%, and the schema itself documents every parameter, including the optionID cross-reference to contests_get and the channel default. The description adds no parameter-specific meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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?

The description states a specific verb (Place) and resource (bet on a contest option), plus the actor (token owner). This clearly distinguishes it from sibling tools like contests_list_bets or contests_get, which list or retrieve contests rather than place bets.

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?

The description gives no when-to-use guidance, no prerequisites (e.g., contest must be open), and does not name alternatives. It simply states the action, leaving the agent to infer context from the name and schema.

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

Deploy Server

Other Tools