Skip to main content
Glama
quantitats

quantitats-mcp

Official
by quantitats
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Place an order

place_order

Submit one real-funds order to a supported venue and get it back as acknowledged. Pass decimal-string quantity and price; LIMIT needs price, stop or take-profit needs stopPrice.

Instructions

Submits one order with real funds and answers with it as the venue acknowledged it. Quantities and prices are decimal STRINGS, not numbers, so nothing is lost to floating point. A LIMIT order needs a price; a stop or take-profit order needs a stopPrice. Check list_instruments first: a price or size off the venue's grid is refused.

Requires the trade:write scope.

Rate limit: 932 requests per minute for your key, shared across every tool in the trade-write group. This is the average of what the supported venues themselves allow one account, so it is not a figure to design around — a strategy that needs more than this needs the venue directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideYesBUY or SELL.
typeYesOrder type.
priceNoLimit price, as a decimal string. Required for LIMIT, LIMIT_MAKER, STOP_LOSS_LIMIT and TAKE_PROFIT_LIMIT.
symbolYesInstrument symbol as the venue lists it, e.g. BTCUSDT.
exchangeYesVenue id, e.g. binance_spot. The market half of the name is part of it.
quantityNoSize in the base asset, as a decimal string.
stopPriceNoTrigger price, as a decimal string. Required for STOP_LOSS, STOP_LOSS_LIMIT, TAKE_PROFIT and TAKE_PROFIT_LIMIT.
reduceOnlyNoOnly meaningful on a derivative venue.
timeInForceNoHow long the order stands. Absent means the venue's default.
quoteQuantityNoSize in the quote asset, as a decimal string. An alternative to quantity, valid only with MARKET.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say it is a non-idempotent, non-read-only, open-world write. The description goes well beyond that: real funds are committed, off-grid prices/sizes are refused, decimal strings are used to avoid floating-point loss, and it discloses the exact shared rate limit with the caveat that it is not a design target.

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?

Four sentences, front-loaded with what the tool does and its cost, then conventions, then preconditions, then limits. The rate-limit sentence is long but the closing caveat ('not a figure to design around') is load-bearing guidance rather than padding.

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?

With no output schema, the description still characterizes the response ('answers with it as the venue acknowledged it'), and it covers auth scope, validation failure mode, numeric encoding, and rate limits. Nothing an agent needs to call this safely is missing.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds real value: it explains the string-not-number convention globally and the conditional requirements for price and stopPrice, reinforcing the schema's per-field notes with a rule-based summary.

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?

States a specific verb and resource ('Submits one order') plus the material consequence ('with real funds'), and the phrase 'one order' distinguishes it from batch/bot siblings like create_bot and cancel_orders. An agent can identify the operation without opening the schema.

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?

Gives a concrete prerequisite ('Check list_instruments first') and states which order types require price vs stopPrice, plus the required trade:write scope. It stops short of naming an alternative tool or an explicit when-not-to-use condition, but the operational context is clear.

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