Skip to main content
Glama

bottrade

by org.bot-trade
OverviewDiscussionsAdmin

Submit a trading decision

submit_decision

Record an explicit hold or trade decision, queue any orders, and advance an authenticated run exactly one bar. This is the normal action after scan_market and inspect_symbols; queued orders fill on the next bar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesDecision type: hold requires no orders; trade requires at least one order.
ordersYesOrders to queue when action is trade; use an empty array when action is hold.
run_idYesRun UUID returned by start_run.
rationaleNoOptional short reason recorded with the decision.
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. Changed8 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"hold or trade."New value: +"Decision type: hold requires no orders; trade requires at least one order."
    • changedInput schema / properties / orders / description
      Previous value: -"Orders."New value: +"Orders to queue when action is trade; use an empty array when action is hold."
    • changedInput schema / properties / orders / items / properties / reasoning / description
      Previous value: -"Reason."New value: +"Optional short reason recorded with this order."
    • addedInput schema / properties / orders / 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 / orders / items / properties / symbol / description
      Previous value: -"Ticker."New value: +"Exact ticker symbol from the scenario universe."
    • changedInput schema / properties / rationale / description
      Previous value: -"Short reason."New value: +"Optional short reason recorded with the decision."
    • 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."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Description adds critical behavioral details beyond annotations: advances exactly one bar, step_count>1 rejected, orders queue and fill next bar. Annotations only indicate not read-only and not destructive.

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 concise sentences that front-load the core purpose and usage context. The description is efficient and informative without unnecessary verbosity.

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?

Despite no output schema, the description explains the tool's effect and sequence position comprehensively. All parameters are documented in schema with additional context in description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds meaningful context for all parameters: action enum meanings, orders array usage, step_count rejection rationale, and run_id/rationale purposes.

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?

Description clearly states it records a hold/trade decision, queues orders, and advances a run exactly one bar. This distinguishes it from siblings like 'step_run' (just advance) and 'submit_turn' (different action).

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 states it's the normal action after scan_market and inspect_symbols, and that orders fill on the next bar. Does not explicitly list when not to use, but the context is clear enough.

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