martingale_reset
Reset the current Martingale session to its initial state, clearing all recorded wins and losses.
Instructions
Reset the current Martingale session to initial state
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Reset the current Martingale session to its initial state, clearing all recorded wins and losses.
Reset the current Martingale session to initial state
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only says 'reset' which implies a destructive state change, but does not disclose what exactly is reset (e.g., session data, history, pending bets) or any side effects. Minimal behavioral disclosure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that efficiently conveys the core purpose. No wasted words, front-loaded with the key action and object.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 is too brief. It does not explain what 'initial state' means, the effect on related tools (e.g., martingale_statistics), or prerequisites. More context would be helpful.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters, so schema description coverage is 100%. With no parameters to explain, the description need not add parameter information. Baseline score of 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'reset' and resource 'current Martingale session' with the outcome 'to initial state'. It distinguishes itself from sibling tools like martingale_init and martingale_record by indicating it resets an ongoing session, but does not explicitly differentiate from other strategy resets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives (e.g., martingale_init). The description implies it is used after a session has been initialized, but does not state when not to use it or provide context about alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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