# Overview (/docs/tools)



The server has four groups of tools. Market data and setup need no
key; the account and trading tools register together as soon as a key is present
(see [Trading](/docs/tools/trading)). Each tool entry lists its parameters,
whether it needs an API key, and a copy-paste example prompt.

You rarely call tools by name. You ask in plain language and the client picks
the tool. The names and parameters here are for reference and for building
agents.

<Cards>
  <Card title="Market Data" href="/docs/tools/market-data" description="Public tools: prices, order book, candles, OI, funding, options, indices. No key." />

  <Card title="Account" href="/docs/tools/account" description="Read-only tools: positions, balances, fills, orders, exports. Read Data key required." />

  <Card title="Trading" href="/docs/tools/trading" description="Place / edit / cancel orders, brackets, leverage, margin, close-all. Registered with any key; a Trading key is what lets them execute." />

  <Card title="Setup" href="/docs/tools/setup" description="Open the key form, save its values, and report what the server is using. Always registered, no key." />
</Cards>

## Conventions [#conventions]

* **Symbols** are Delta product symbols, e.g. `BTCUSD` (perp) or
  `C-BTC-66400-010824` (option).
* **Timestamps** in candle/history tools are **Unix seconds**; in
  fills/orders/wallet history they are **microseconds** (`*_us`).
* **Paginated** tools return a `meta.after` cursor; pass it back to fetch the
  next page.
* **Auth badge** on each tool is the source of truth for whether a key is
  needed, regardless of which group it sits in.

<Callout title="Verify against your installed version">
  Tool names and parameters reflect the current server build. Run
  `uvx delta-exchange-mcp` and inspect your client's tool list to confirm what
  your installed version exposes.
</Callout>