tradefloor

Overview Schema Source Related Servers Discussions Admin

Start a background simulation

start_job

Start background runs of strategy evaluations, rankings, or stress scenarios and return a job ID at once; use for 252-day horizons, then poll with check_job.

Instructions

Start a long run of evaluate_strategies, rank_strategies or run_stress_scenario in the background and get a job id back immediately. This is the ONLY way to run to the certified 252-day horizon; a direct call is capped at 60 days so it can answer inside a conversation. The arguments are checked before the job starts, and the response estimates its run time. At most 2 jobs run at once and the last 32 are kept, in this server's memory only. A preset or population in the arguments is checked before the job starts. Poll with check_job.

Input Schema

Name	Required	Description	Default
`tool`	Yes	The tool to run in the background.
`arguments`	No	That tool's arguments, as a direct call takes them. days may go to 252. An unknown argument or a wrong type is refused before the job starts.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (readOnly=false, non-idempotent, non-destructive), it discloses async semantics, capacity limits ('at most 2 jobs run at once'), retention ('last 32 are kept'), ephemerality ('in this server's memory only'), pre-start argument validation, and a runtime estimate in the response. This is unusually rich operational context for a mutation-style tool.

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?

Front-loaded with purpose, then constraints, then the polling pointer — good ordering. It loses a point for near-duplication: 'The arguments are checked before the job starts' is repeated as 'A preset or population in the arguments is checked before the job starts.'

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?

With an output schema present, return values need not be explained, and the description still covers async behavior, limits, persistence, and validation. Nothing an agent needs to invoke it correctly and then follow up 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 description coverage is 100% and both parameters are documented, so the baseline is 3. The description mostly restates schema content (the 252-day limit, refusal of unknown args/wrong types); the only added nuance is that a 'preset' or 'population' gets validated, which is marginal.

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 ('Start') plus the exact resources it wraps (evaluate_strategies, rank_strategies, run_stress_scenario) and the immediate return (a job id). This lets an agent distinguish it from the direct sibling calls without opening any 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?

Explicit when-to-use: it is 'the ONLY way to run to the certified 252-day horizon', contrasted against the direct call which 'is capped at 60 days so it can answer inside a conversation'. It also names check_job as the polling alternative, so both the use and follow-up path are stated.

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