Skip to main content
Glama

bottrade

by org.bot-trade
OverviewDiscussionsAdmin

Get raw market bars

get_market
Read-only

Return raw bars at the current simulator time for an authenticated run, optionally limited to selected symbols. This read-only advanced-data path enforces a 500-row budget; the compact workflow is scan_market followed by inspect_symbols.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYesRun UUID returned by start_run.
symbolsNoOptional symbol subset. Omit only when lookback is 1; larger whole-universe requests are rejected.
lookbackNoNumber of bars to return per symbol; the total request must remain within the server's 500-row budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / lookback / description
      Previous value: -"Bars per symbol."New value: +"Number of bars to return per symbol; the total request must remain within the server's 500-row budget."
    • changedInput schema / properties / run_id / description
      Previous value: -"Run UUID."New value: +"Run UUID returned by start_run."
    • changedInput schema / properties / symbols / description
      Previous value: -"Optional symbol subset. Omit only with lookback=1."New value: +"Optional symbol subset. Omit only when lookback is 1; larger whole-universe requests are rejected."
    • changedInput schema / properties / symbols / items / description
      Previous value: -"Ticker symbol from the scenario universe."New value: +"Exact ticker symbol from the scenario universe."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds behavioral context (500-row budget, current simulator time, enforced limits) that goes beyond annotations without contradicting them.

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 efficient sentences. First sentence covers purpose and key constraints; second sentence positions the tool among siblings. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description adequately covers behavior given 3 parameters and no output schema. It explains the read-only nature, budget, and alternatives. Minor omission: could briefly describe the output format (raw bars structure).

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?

With 100% schema coverage, baseline is 3. The description adds meaning by explaining the 500-row budget and when symbol omission is allowed, aiding understanding beyond the raw schema.

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 returns raw bars at current simulator time for an authenticated run, optionally limited to symbols. It distinguishes from siblings by contrasting with the compact scan_market + inspect_symbols workflow.

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?

The description provides clear context for use (advanced-data path, 500-row budget) and mentions an alternative workflow. However, it does not explicitly state when not to use this tool, leaving some ambiguity.

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