Skip to main content
Glama

Get Authoring Reference

tt_get_authoring_reference
Read-onlyIdempotent

On-demand DEEP authoring reference for ONE topic — the heavy cookbook / detail sections that the lean quickstart no longer carries inline.

Topics (call with no argument for the authoritative menu): common_patterns, wire_vs_display_forms, equity_vs_derivatives_legs, option_chain_recipes, repair_once_pattern, capability_map, exit_sl_target, markdown_grammar_extended, candle_timeframes, frozen_instrument, python_block, list_based, strategy_brief_template, positional_mechanics, adjustments_taxonomy, adjustments_crosswalk, webhook_linking, editing_existing_strategies.

★ strategy_brief_template is the one topic meant for the USER, not for you: serve it VERBATIM when someone asks "what prompt/format should I use", "is there a standard template", or "how do I stop it changing things I didn't ask for".

The quickstart's CORE keeps only a compact OUTLINE/mandate of each plus a pointer here. While composing a strategy, pull the ONE topic you need — do NOT pull all of them. Call with no topic to list the menu with one-line descriptions.

For full worked strategy TEMPLATES (iron condor, strangle, ...) use tt_get_sample_strategy(pattern) instead — that returns runnable payloads, this returns reference prose/snippets.

Args: topic: one of the published topics above (empty → the menu index).

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

Input Schema

NameRequiredDescriptionDefault
topicNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the safety profile needs no repetition. Beyond that, the description discloses the return content type (reference prose/snippets vs. runnable payloads) and the empty-argument menu behavior. It does not say anything about response size or pagination for large topics, which is the only remaining gap.

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 the topic enumeration, then the routing rule and the special-case note. The 18-item topic list is long but earns its place because the schema carries no enum. The bullets and ★ marker keep it scannable; minor tightening of the closing "Args" restatement would make it cleaner.

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?

With one optional parameter, no output schema and full annotation coverage, an agent has everything needed to call it correctly and know what comes back (prose/snippets). Only the shape/size of the returned reference body is left unspecified, which is minor for a lookup tool.

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 0% — the schema only says `topic` is a string defaulting to empty. The description compensates fully by enumerating all 18 valid topic values and explaining that an empty value yields the menu index with one-line descriptions, which is meaning no schema field provides.

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+resource ("DEEP authoring reference for ONE topic") and scopes it as the heavy cookbook detail the lean quickstart no longer carries. It explicitly contrasts with tt_get_sample_strategy, so an agent can distinguish reference prose/snippets from runnable payloads 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 explicit when-to-use ("While composing a strategy, pull the ONE topic you need"), an explicit when-not ("do NOT pull all of them"), a no-argument behavior (returns the authoritative menu), and a named alternative for templates. It also flags the strategy_brief_template special case with trigger phrases and how to serve it verbatim.

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