Skip to main content
Glama

Draft a bot setup

draft_bot
Read-only

Drafts a bot on Angler's Bots page as a link that opens its window filled in: a grid bot (price range, grid count, investment), a market maker (spread, levels, quote size, inventory and loss caps) or a funding pair (long on one venue, short on another; once, held for funding, for volume, or for open interest rewards). It starts nothing: the user opens the link, checks the setup and starts it themselves. Bots run in the user's browser tab.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>"
    },
    "name": "draft_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNogrid / market_maker: the venue's market name, usually the ticker (BTC).
modeNogrid: neutral (default), long or short. funding_pair: once, hold (default), volume or oi.
typeYes
gridsNogrid: default 10.
venueNogrid / market_maker: the venue id (e.g. hyperliquid).
levelsNomarket_maker: default 2.
symbolNofunding_pair: the asset ticker.
leverageNoDefault 2.
size_usdNomarket_maker: each quote's size.
step_bpsNomarket_maker: default 5.
long_venueNo
spread_bpsNomarket_maker: default 10.
lower_priceNo
short_venueNo
upper_priceNo
max_loss_usdNo
investment_usdNogrid: margin put in.
max_inventory_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description is consistent with them, reinforcing that nothing is started. It adds genuinely useful behavior beyond the annotations: the output is a link that opens a pre-filled window, and bots execute in the user's browser tab rather than server-side.

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?

Purpose is front-loaded, followed by the type breakdown and then the critical "it starts nothing" caveat. The parenthetical enumerations are dense but each sentence carries information an agent needs; no filler is present.

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

Completeness4/5

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

For an 18-parameter tool with no output schema, it covers the essential unstated facts: the return value is a shareable link, the draft is inert, and execution happens client-side. It leaves default values and the significance of the required "type" field to the schema, which is acceptable.

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 18 parameters at 61% schema coverage, the description adds real meaning by grouping parameters per bot type (price range, grid count, investment; spread, levels, quote size, inventory and loss caps; long/short venue pairings and the once/hold/volume/oi modes). Some parameters such as leverage, coin, and venue-vs-symbol distinctions are still left entirely to the 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 names a specific verb ("Drafts") and resource ("a bot on Angler's Bots page") and immediately enumerates the three bot types it supports with their key settings. It is clearly distinguishable from the order-drafting sibling because of the explicit bot-type taxonomy (grid, market maker, funding pair).

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?

It supplies the decisive usage context: the tool produces a link, starts nothing, and the user opens the link and starts the bot themselves. It does not, however, tell the agent when to pick one bot type over another, or when a sibling such as draft_order would be the better call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources