Skip to main content
Glama
Sign In
TradeStaq MCP

TradeStaq MCP

Official
by the-staq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

explain_strategy

Get a plain-English explanation of a strategy: what it does, risk profile, best market conditions.

Instructions

Get a plain-English explanation of a strategy: what it does, risk profile, best market conditions.

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": {
      "id": "<id>"
    },
    "name": "explain_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStrategy ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses outputs (what it does, risk profile, market conditions) but does not mention any behavioral traits like no side effects, data freshness, or required permissions.

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

Conciseness5/5

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

A single, concise sentence that is front-loaded with the main purpose and includes key details. No wasted words.

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?

For a simple tool with one parameter and no output schema, the description adequately covers purpose and outputs. Could be improved by mentioning that the explanation is generated or based on historical data, but it is already fairly complete.

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% for the single 'id' parameter. The tool description adds no additional meaning beyond the schema's 'Strategy ID', so baseline 3 is appropriate.

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 clearly states the tool provides a 'plain-English explanation of a strategy' and specifies what it covers: functionality, risk profile, and best market conditions. This is specific and distinct from sibling tools like 'get_strategy' which likely returns raw data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use (when an explanation is needed) but provides no explicit guidance on when not to use or alternatives among siblings like 'get_strategy' or 'compare_strategies'.

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

Deploy Server

Other Tools