Skip to main content
Glama

Load Strategy Authoring Quickstart

tt_get_tradetron_quickstart
Read-onlyIdempotent

Lean strategy-AUTHORING context bundle (navigation, safety, interview, schema-rule locks, type enums, catalog index, worked-example outlines). ~50k chars (~13k tokens) — the heavy cookbooks are deferred to tt_get_authoring_reference(topic), pulled on demand. (The two different sizes this description used to give, 5k tokens here and 18k below, were both wrong and neither matched the payload.)

CALL THIS ONLY WHEN THE USER WANTS TO CREATE OR EDIT A STRATEGY, and only once per session before you start composing. Calling it cuts the 5-10 speculative authoring lookups down to 1.

DO NOT call it for anything else — diagnosing why a strategy errored (tt_diagnose_strategy), performance/P&L (tt_strategy_performance, tt_portfolio_report), account/plan/pricing questions, or general chat. Those tools are self-contained and pulling this much authoring schema in front of them just adds latency. When in doubt, DON'T call it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tt_get_tradetron_quickstart"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds what they cannot: the payload weight (~50k chars, ~13k tokens), the latency tradeoff of pulling authoring schema in front of unrelated tools, and the payoff (cutting 5-10 speculative lookups to 1). That is exactly the cost/benefit an agent needs before spending context budget.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The trigger/exclusion block is front-loaded and tight, but the trailing parenthetical about the two previous token figures (5k here, 18k below) both being wrong and matching neither payload is self-referential changelog noise that confuses rather than informs. A reader has to parse a correction to a claim that is no longer in the text — that sentence does not earn its place.

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 zero-argument context-loading tool with no output schema, the description covers everything that matters: what is inside the bundle, how large it is, when to pull it, when not to, and where the deferred detail lives. No return-value documentation is needed since no output schema exists and the content is described.

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?

The tool takes zero parameters and the schema is an empty object, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misdescribes or omits an argument.

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?

Names a specific verb+resource (loads a strategy-AUTHORING context bundle) and enumerates the payload contents (navigation, safety, interview, schema-rule locks, type enums, catalog index, worked-example outlines). It explicitly positions itself against tt_get_authoring_reference, which it says holds the heavy cookbooks pulled on demand, so the agent can separate the two without opening either 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?

Gives an explicit positive trigger (user wants to create or edit a strategy), a frequency constraint (once per session before composing), and a named exclusion list with reasoning — tt_diagnose_strategy for error diagnosis, tt_strategy_performance and tt_portfolio_report for P&L. It closes with a tie-breaker default ("When in doubt, DON'T call it"), leaving nothing to inference.

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