Skip to main content
Glama

Place market orders

place_orders
Destructive

Put 1-50 limit orders (BUY or SELL at your own price) into the order book; they fill later when someone matches. For an instant trade at the station price use buy/sell instead. See them with my_orders, withdraw with cancel_order. Each entry is {item_code, type: BUY | SELL, quantity, price}. Broker fee is paid when placing, buy tax when a BUY fills. Needs docking and funds; the reply lists success or error per entry, a failed entry does not stop the others.

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": {
      "orders": "<orders>"
    },
    "name": "place_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
bearerNoYour SPACE-CORE Bearer token. Only needed if your client cannot send the Authorization header.
ordersYesList of 1-50 orders, each {item_code, type, quantity, price}, e.g. [{"item_code":"RAW_TITANIUM","type":"SELL","quantity":10,"price":12.5}] (a JSON text of the array is also accepted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / orders / items / properties / price / description
      Previous value: -"Price per unit in CWM (>= 0.01)"New value: +"Price per unit in CWM (>= 1)"
  2. Changed1 schema field changed
    • changedInput schema / properties / orders / description
      Previous value: -"List of 1-50 orders, each {item_code, type, quantity, price}, e.g. [{\"item_code\":\"RAW_IRON\",\"type\":\"SELL\",\"quantity\":10,\"price\":12.5}] (a JSON text of the array is also accepted)"New value: +"List of 1-50 orders, each {item_code, type, quantity, price}, e.g. [{\"item_code\":\"RAW_TITANIUM\",\"type\":\"SELL\",\"quantity\":10,\"price\":12.5}] (a JSON text of the array is also accepted)"
  3. Changed3 schema fields changed
    • changedInput schema / properties / orders / description
      Previous value: -"List of orders, max 50 (a JSON text of the array is also accepted)"New value: +"List of 1-50 orders, each {item_code, type, quantity, price}, e.g. [{\"item_code\":\"RAW_IRON\",\"type\":\"SELL\",\"quantity\":10,\"price\":12.5}] (a JSON text of the array is also accepted)"
    • addedInput schema / properties / orders / items / properties / item_code / description
      Added value: +"Item code, e.g. RAW_TITANIUM"
    • addedInput schema / properties / orders / items / properties / quantity / description
      Added value: +"Units to buy or sell (integer >= 1)"
  4. Changed1 schema field changed
    • addedInput schema / properties / bearer / description
      Added value: +"Your SPACE-CORE Bearer token. Only needed if your client cannot send the Authorization header."
  5. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations say destructive, non-idempotent, non-readonly; the description adds real context beyond that — broker fee charged on placement, buy tax on fill, docking and funds prerequisites, and per-entry success/error with partial-failure semantics.

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?

One dense paragraph with no filler: the core action leads, the disambiguation and related tools follow, then the entry format, fees, prerequisites, and response semantics. Every clause carries information.

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?

For a two-parameter mutation with no output schema, it covers prerequisites (docking, funds), cost model, and the shape of the reply including per-entry failure isolation — everything needed to call it correctly.

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 100%, so the baseline is 3, but the description still adds meaning: price is a limit price rather than a market price that fills later, and the entry object shape is spelled out in prose. It largely restates the schema's structure, keeping it just below top marks.

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 — placing 1-50 limit orders into the order book — and contrasts it with the instant-trade siblings buy/sell, so an agent can distinguish it 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 Guidelines5/5

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

Explicitly routes: use this for limit orders at your own price, use buy/sell for an instant trade at the station price, my_orders to view, cancel_order to withdraw. When-to-use and alternatives are both named.

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