Skip to main content
Glama
Sign In
OctoBot MCP Server

OctoBot MCP Server

by roman-zaglauer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

clear_trades_history

Permanently delete OctoBot's stored trade history after explicit confirmation, preventing accidental data loss.

Instructions

Permanently clear OctoBot's stored trades history. Confirm-gated (ADR-0003).

If confirm is not exactly true, no OctoBot call is made at all -- this returns require_confirmation's structured refusal (a normal return, not an error) instead.

Once confirmed, maps to POST /api/clear_trades_history ([V], re-confirmed against source this session -- see this module's docstring). Returns OctoBot's own JSON body unchanged (NFR-8): {"title": "Cleared trades history"}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clear_trades_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden, and it excels: it discloses permanent destruction, confirms no side effects unless `confirm` is true, explains that the refusal path is a normal return rather than an error, maps to the exact endpoint, and specifies the response body.

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 description is well-organized and front-loaded with the core purpose, followed by confirmation semantics, endpoint mapping, and return shape. Minor internal references such as ADR-0003, NFR-8, and module docstring are not strictly actionable for an agent, so the prose is slightly less lean than it could be.

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

Completeness5/5

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

For a one-parameter destructive tool with no output schema, this description is complete: it covers the required confirmation flag, side effects, non-error refusal behavior, endpoint, and exact successful response. An agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain the `confirm` parameter, and it does: `true` triggers clearing, anything else returns a structured refusal without calling OctoBot. This adds substantial meaning beyond the bare boolean schema.

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 uses a specific verb+resource pair ('Permanently clear OctoBot's stored trades history') and leaves no doubt about the target data. It also naturally distinguishes this tool from sibling clear_* tools by naming 'trades history' specifically.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear invocation conditions are provided: the call is confirm-gated, and if `confirm` is not exactly `true` no OctoBot call occurs. However, it does not explicitly contrast this tool with alternatives like `clear_orders_history` or `clear_transactions_history`; the differentiation is left to the name and description.

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