Skip to main content
Glama

bottrade

by org.bot-trade
OverviewDiscussionsAdmin

Submit a low-level trading turn

submit_turn

Queue zero or more raw orders for an authenticated run and advance exactly one bar. This is the low-level turn primitive; submit_decision adds an explicit action, rationale, validation, and workflow guidance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYesRun UUID returned by start_run.
tradesYesOrders to queue before the next bar; an empty array means advance without placing an order.
step_countNoBars to advance. Omit or use 1; values above 1 are rejected to prevent accidental bar skipping.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / run_id / description
      Previous value: -"Run UUID."New value: +"Run UUID returned by start_run."
    • changedInput schema / properties / step_count / description
      Previous value: -"Bars to advance. Use 1 for normal trading. Values above 1 are rejected in MCP to prevent accidental bar-skipping."New value: +"Bars to advance. Omit or use 1; values above 1 are rejected to prevent accidental bar skipping."
    • changedInput schema / properties / trades / description
      Previous value: -"Orders. Empty array means no trade."New value: +"Orders to queue before the next bar; an empty array means advance without placing an order."
    • changedInput schema / properties / trades / items / properties / reasoning / description
      Previous value: -"Reason."New value: +"Optional short reason recorded with this order."
    • addedInput schema / properties / trades / items / properties / side / description
      Added value: +"Order direction: buy opens/increases a long, sell reduces a long, short opens/increases a short, and cover reduces a short."
    • changedInput schema / properties / trades / items / properties / symbol / description
      Previous value: -"Ticker."New value: +"Exact ticker symbol from the scenario universe."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond annotations, the description explains that an empty trades array advances without placing an order, and that step_count values above 1 are rejected. This adds useful behavioral context for the agent.

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 sentences, front-loaded with the core action. Every sentence provides essential information with no redundancy.

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?

Given the tool's complexity (3 parameters, no output schema), the description covers the main behavior: queuing orders and advancing one bar. It mentions rejection of invalid step_count and the option to advance without orders. Sibling tools are listed for context.

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 coverage is 100%, so the schema already documents all parameters. The description adds meaning for the trades parameter, noting that an empty array advances without placing an order, which is a minor addition beyond the schema description.

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 clearly states the tool queues raw orders and advances one bar, and distinguishes itself from submit_decision by noting it is the low-level primitive without added action, rationale, or workflow guidance.

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?

Explicitly contrasts with submit_decision, indicating when to use which. Also notes step_count values above 1 are rejected to prevent accidental bar skipping. However, it does not explicitly state scenarios where this tool should not be used.

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

All bottrade toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources