Skip to main content
Glama

Ask Tradetron (Knowledge Base)

tt_ask_tt
Read-onlyIdempotent

Ask TT — answer any question about Tradetron from the indexed knowledge base (FAQ, help docs, blog, forum). Cites sources.

USE WHEN: user asks about Tradetron product features, capabilities, pricing tiers, common workflows, "can I do X on Tradetron", "how do I Y", or any question ABOUT TRADETRON-AS-A-PLATFORM (NOT about authoring a specific strategy).

DO NOT USE for:

  • Broker-support questions ("do you support X?", "what brokers are connected?", "any US brokers?") → use tt_check_broker_support or tt_list_brokers. Those are deterministic against a bundled catalog; this tool is RAG-based and may miss or misreport.

  • Authoring a new strategy → use tt_create_strategy + the validate / keyword-lookup tools instead.

  • Editing / fetching an existing strategy → use tt_get_strategy / tt_update_strategy.

  • Looking up a specific keyword → use tt_lookup_keyword.

Returns a structured retrieval result for the calling assistant to turn into the user-facing answer. The result describes how it was assembled (synthesis_instructions):

  • definitive_no_answer non-null → Tradetron has no such feature; the field carries the exact wording so the answer is not an invented workaround.

  • escalate=True → the knowledge base cannot answer; the handoff_payload lets the user reach a support agent (tt_open_support_conversation).

  • Otherwise the answer is grounded in the cited sources; include a source URL inline when a source carries one (catalog-backed sources have a title but no URL — cite them by name).

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": {
      "query": "<query>"
    },
    "name": "tt_ask_tt"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds what annotations cannot: the retrieval is RAG-based and can be incomplete, and the response carries synthesis_instructions with definitive_no_answer, escalate/handoff_payload, and per-source citation rules (catalog-backed sources have a title but no URL). It also names a follow-on tool (tt_open_support_conversation) for the escalation path.

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?

The description is long but front-loaded and sectioned: purpose first, then USE WHEN, then DO NOT USE, then return shape. The return-value paragraph is necessary because there is no output schema; the only mild cost is repetition of 'Tradetron' and a somewhat dense final paragraph.

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 no output schema and a single bare parameter, the description still tells the agent exactly how to interpret the response and how to render the final answer, including source citation and no-answer/escalation handling. Nothing needed 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% with a single required 'query' string, so the schema adds nothing beyond type. The description compensates by delimiting what kinds of queries belong here (platform-level features, pricing, workflows) versus strategy authoring or keyword lookup, which constrains how to phrase the query.

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 opens with a specific verb and named resource: 'answer any question about Tradetron from the indexed knowledge base (FAQ, help docs, blog, forum).' It also states the source basis and that it cites sources, which separates it from sibling tools that read the same data deterministically.

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 gives an explicit USE WHEN block with concrete phrasings ('can I do X', 'how do I Y') and a DO NOT USE block that names the preferred alternative for each excluded case (tt_check_broker_support, tt_list_brokers, tt_create_strategy, tt_get_strategy, tt_update_strategy, tt_lookup_keyword). The broker-support exclusion even explains why the alternative is better: deterministic catalog vs. RAG that 'may miss or misreport.'

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