Skip to main content
Glama
Gainium

Gainium

Official

create_bot

Destructive

Create a trading bot on Gainium in one step with all settings passed directly, eliminating the need for a separate update call.

Instructions

Create a new bot in a single step — no follow-up update needed. The top-level properties cover the most common fields. For any field from discover(target: "bot") that is NOT listed here (e.g. startOrderType, useMoveTP, moveTPTrigger, moveTPValue, stopLossTimeout, takeProfitTimeout, dcaOrdersMultiplier, dcaStepMultiplier, trailingTP, trailingTPPerc, indicators, timers, and any other discovery field), pass them inside the 'settings' object — it is transparently merged into the request body at creation time. This avoids a create→update two-step. Use discover(target: 'bot', botType) to discover all available fields and defaults. The 'futures' and 'coinm' fields are auto-detected from the exchange — do not provide them. Requires write API key permission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
botTypeYesBot type
exchangeUUIDYesUUID of the exchange connection to use
paperContextNoPaper trading context (true = paper, false = real). Default: false
pairYesTrading pairs as array of {base}_{quote} strings, e.g. ["BTC_USDT"]. For Grid bots pass a single-element array — the server unwraps it automatically.
nameNoBot name
strategyNoTrading direction. Default: LONG
baseOrderSizeNoSize of the initial base order, e.g. "100"
orderSizeNoSize of each DCA/grid order, e.g. "100"
orderSizeTypeNoOrder size reference currency. Default: quote
tpPercNoTake profit percentage, e.g. "1.5"
slPercNoStop loss percentage, e.g. "-10"
stepNoPrice deviation % for next DCA/grid order, e.g. "1.5"
ordersCountNoMaximum number of orders (DCA/Combo)
gridLevelNoGrid level count (Combo only)
maxNumberOfOpenDealsNoMaximum concurrent open deals, e.g. "1"
topPriceNoTop price for grid range (Grid only)
lowPriceNoLow price for grid range (Grid only)
budgetNoTotal budget for grid (Grid only)
levelsNoNumber of grid levels (Grid only)
gridTypeNoGrid distribution type (Grid only)
startConditionNoCondition to start a new deal. Default: ASAP
useDcaNoEnable DCA orders. Set false for a single base-order bot.
useSlNoEnable stop-loss. When true, slPerc is used.
moveSLNoEnable trailing stop-loss (move SL as price moves in your favour).
moveSLTriggerNoProfit % at which trailing SL is activated, e.g. "1.0"
moveSLValueNoTrail distance % for the moving SL, e.g. "0.5"
startOrderTypeNoOrder type for the base (start) order. Default: market
settingsNoTransparent passthrough for any bot settings field from discover(target: "bot") that is not listed as a top-level property above. All keys are merged flat into the request body — use this to create a fully-configured bot in a single call.
Behavior4/5

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

Annotations already indicate destructiveHint=true, so the description's mention of creation implies mutation. The description adds value by explaining the single-step behavior and transparent merging of settings, which goes beyond the annotations. No contradiction detected.

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 a single paragraph with key points front-loaded (single step creation, settings fallback). It is efficient and every sentence provides useful information. However, it could be more structured with bullet points for clarity.

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?

Given the tool's complexity (28 parameters, nested objects, no output schema), the description covers the creation process well. However, it does not describe the return value or confirmation of success, which is a gap. The lack of output schema increases the burden on the description.

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?

With 100% schema coverage, the baseline is 3. The description adds meaning for the 'settings' parameter, explaining it is a transparent passthrough for any field not listed. It also provides additional context for 'pair' (Grid bot unwrapping) and enumerates examples of fields that go into settings. This elevates the score above baseline.

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 it creates a new bot in a single step, avoiding the need for a follow-up update. This directly specifies the verb and resource, and the phrase 'no follow-up update needed' distinguishes it from sibling tools like update_bot.

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?

The description provides explicit guidance on using the 'settings' object for fields not listed, and references discover() for all available fields. It also warns about auto-detected fields ('futures', 'coinm') and clarifies pair handling for Grid bots. However, it does not explicitly state when not to use this tool or provide alternative tool names.

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/Gainium/gainium-mcp'

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