Skip to main content
Glama

Get Sample Strategy Template

tt_get_sample_strategy
Read-onlyIdempotent

Return a worked, real strategy template for a named pattern, or a validated reference from the category-tier sample library. Call with no pattern to list everything.

Scope: ~18 top-level patterns (iron_condor, short_strangle, short_straddle, butterfly, rolling_straddle, calendar, exchange exemplars — mcx_sample_template, delta_crypto, us_spx_condor, sensex_orb, nse_sample, nfo_samples — and mechanics/references — repair_once_best_practice, staged_reentry, wait_and_trade, pilot_calm, canonical, rank_top_gainers_losers) AND a library of 140+ validated entries in 7 categories (option_patterns, team_idioms, primitives, gap_structures, gap_entries, mechanics, chart_types). pattern='library' -> the category menu; pattern= -> its entries; pattern=<entry key or a fragment of it, e.g. 'pmcc'> -> the entry. The registry is data-driven — the no-pattern call, not this docstring, is the authoritative list.

Use this INSTEAD of carrying full examples in the quickstart — pull the one pattern you need, study its mechanics + reference_json/markdown, then author + tt_validate_markdown before create. Never fabricate a strategy for an unlisted pattern — the tool returns the catalog.

Args: pattern: A pattern name / alias (straddle, strangle, ic, condor, fly, mcx, crypto, us, sensex, orb, ...), 'library', a library category, or a library entry key/fragment. Empty -> patterns + categories. fmt: auto | json | reference. All include the verified reference_json when one is bundled.

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_sample_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
fmtNoOne of: auto, json, reference. Default 'auto'. Matched case-insensitively.auto
patternNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), but the description adds real behavior: the registry is data-driven, the no-pattern call is the authoritative list rather than the docstring, and every fmt mode bundles the verified reference_json when present. The only gap is that it says nothing about response size for the 140+ entry library listing, which matters for a read that can return a large catalog.

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?

Well structured with front-loaded capability statement followed by Scope, Usage, and Args sections, and no sentence is filler. The one inefficiency is the long enumerated pattern and category catalog, which the description itself declares non-authoritative ('the no-pattern call, not this docstring, is the authoritative list'), so part of that enumeration is self-admitted redundancy.

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 2-parameter, no-output-schema, read-only lookup tool, the definition covers everything an agent needs: what it returns (mechanics plus reference_json/markdown), how to enumerate instead of guessing keys, and the mandatory follow-up step before creating a strategy. No return-value contract is left unexplained.

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 only 50% and the `pattern` parameter has no schema description at all, so this text carries the burden and does so thoroughly: it documents aliases (straddle, ic, fly, mcx, crypto), the special 'library' value, category names, entry keys or fragments like 'pmcc', and the empty-string default meaning. It also explains fmt's three modes and what all of them include.

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 and resource: return a worked strategy template for a named pattern, or a validated reference from a category-tier sample library, and lists the concrete pattern/key space it serves. An agent can distinguish it from tt_get_authoring_reference or tt_get_tradetron_quickstart because it explicitly says it replaces carrying full examples in the quickstart.

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 explicit routing rules: pull one pattern, study its mechanics plus reference_json/markdown, then author and run tt_validate_markdown before create; call with no pattern to list everything; pattern='library' for the menu; never fabricate a strategy for an unlisted pattern. It names the downstream alternative (tt_validate_markdown) and the exact condition that selects it.

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