Skip to main content
Glama

Check a strategy build's progress

acubic_get_build_status
Read-onlyIdempotent

Tracks a new draft from acubic_create_strategy by its build_id while it is assembled: progress and poll_after_seconds, then the saved strategy's id to open once. A failed or cancelled build is an error that cost nothing. Backtests have acubic_get_backtest_status.

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": {
      "build_id": "<build_id>"
    },
    "name": "acubic_get_build_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoThe language of this conversation.
build_idYesThe build_id acubic_create_strategy returned.

Output Schema

NameRequiredDescriptionDefault
buildNo
errorNo
disclosureNo
next_stepsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral facts: the response carries progress and a poll_after_seconds cadence, a failed or cancelled build surfaces as an error, and such failure 'cost[s] nothing'. That phrase is slightly opaque (no credit consumed?) but signals a meaningful side-effect-free failure mode.

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?

Two dense sentences with no filler, front-loading the lifecycle and polling behavior before the alternative-tool pointer. Minor density cost comes from the clipped phrase 'an error that cost nothing', which reads as shorthand rather than plain language.

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, read-only status tool with an output schema, the description covers the full lifecycle: what is returned, how often to poll, what terminal success looks like, how failure is reported, and which sibling handles the analogous backtest case. Nothing an agent needs in order to call it correctly is missing.

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 both parameters are already documented, including build_id's provenance from acubic_create_strategy and the locale enum. The description reinforces that build_id comes from the create call but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 states a specific verb and resource ('tracks a new draft ... by its build_id while it is assembled') and anchors it to the originating tool, acubic_create_strategy. It also explicitly separates itself from the backtest equivalent ('Backtests have acubic_get_backtest_status'), so an agent can distinguish it from siblings 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?

It says exactly when to call it (while the build is assembling), how to pace calls (use the returned poll_after_seconds), and when to stop (once the saved strategy's id appears). It also names the alternate tool for a different object type, closing the main routing ambiguity.

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