Skip to main content
Glama
yusakuvol

Betting Method MCP Server

by yusakuvol

cocomo_init

Initialize a Cocomo betting session by providing a base unit amount. Optionally set a maximum bet limit to control risk.

Instructions

Initialize a new Cocomo betting session with base unit and optional max bet limit

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxBetNoMaximum bet amount (optional, default: baseUnit × 1000)
baseUnitYesThe base unit amount for betting (e.g., 1, 10, 100)
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It only states 'initialize' without explaining side effects (e.g., does it reset existing sessions? is it destructive?) or any state changes. Missing details on prerequisites or the implications of the optional maxBet parameter.

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?

Single sentence with 14 words, front-loaded with action. No redundant information. Highly efficient.

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

Completeness2/5

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

Given no output schema and no annotations, the description should explain what 'initialize' entails (e.g., session creation, previous session handling). It lacks crucial behavioral context for an initialization tool in a betting strategy system.

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%, with clear explanations of baseUnit and maxBet (including default). The description adds minimal value by restating 'base unit and optional max bet limit'. 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 clearly states the tool initializes a new Cocomo betting session, specifying the parameters (base unit and optional max bet). The verb 'Initialize' and resource 'Cocomo betting session' are unambiguous, and the tool name distinguishes it from sibling strategy init tools.

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 on when to use Cocomo versus other betting strategies (e.g., martingale, dalembert). The description does not mention prerequisites, conditions, or context for using this tool over alternatives.

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/yusakuvol/betting-method-mcp'

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