Skip to main content
Glama
Gainium

Gainium

Official

apply_preset

Destructive

Fetch a curated strategy preset and create a bot in one call. Specify coin, exchange, tier, and strategy; optionally override pair, name, or sizing.

Instructions

Create a bot from a curated preset in one call: fetches the preset for the given coin/exchange/tier/strategy, then creates a bot from its settings. Override pair, name, or sizing as needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
botTypeYesBot type
coinYesBase asset, e.g. "BTC"
exchangeYesPreset exchange, e.g. "binance"
tierYesRisk tier: short (tight), mid (balanced), long (wide)
strategyNoDirection (default "long")
exchangeUUIDYesUUID of YOUR connected exchange to create the bot on (from get_account info:"exchanges")
paperContextNoPaper trading context (true = paper, false = real). Default: false
pairNoOverride the preset pair(s), underscore format e.g. ["BTC_USDT"] (optional)
nameNoOverride the bot name (optional)
Behavior3/5

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

Annotations already indicate destructive hint. Description adds process detail but no additional behavioral traits beyond annotations. Consistent with destructive nature.

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?

Two concise sentences, front-loaded with purpose, no fluff. Every word earns its place.

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?

Describes process and overrides but lacks output details. With 9 params and no output schema, description could mention return value. Adequate but not 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 has 100% coverage, so baseline 3. Description mentions override pair and name but incorrectly includes 'sizing' which is not a parameter, causing slight confusion. No net gain over 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?

Description clearly states the tool creates a bot from a curated preset in one call, distinguishing it from manual creation (create_bot) or listing presets (list_presets). It specifies the process and overrides.

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

Usage Guidelines3/5

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

Description implies use for presets but lacks explicit guidance on when to use vs alternatives like create_bot. No when-not-to or exclusions provided.

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