Skip to main content
Glama

Strategy rules

get_strategy
Read-only

One strategy's rules: the buy, add, exit and trim conditions as the engine reads them, each with its words as the Strategies page shows them, and the same strategy in the page's Export JSON shape. A deleted strategy is still returned, since its old signals name it.

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": "get_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe strategy id, from get_strategies or a signal's strategy_id.

Output Schema

NameRequiredDescriptionDefault
errorNo
rulesNo
exportNo
strategyNo
warningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / error / properties / reason
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / warnings
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavior beyond that: deleted strategies are returned rather than erroring, and the response carries three parallel renderings of the same rules. That is genuinely useful context an agent would not otherwise know.

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?

Two sentences, content front-loaded on what is returned, with the deleted-strategy caveat placed after. The first sentence is long and packed with subordinate clauses, which costs a little readability, but no wording is wasted.

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 an output schema present, the description is not obligated to explain return values, yet it still characterizes their shape well enough for an agent to know what it is getting. For a single-parameter read tool with full annotation coverage, nothing essential is missing.

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% and the single id parameter already documents its provenance (from get_strategies or a signal's strategy_id). The description adds no further meaning about the id, so the baseline 3 applies.

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 names a specific resource (one strategy) and enumerates exactly what comes back: buy/add/exit/trim conditions as the engine reads them, the page's wording, and the Export JSON shape. The singular framing plus the unusual engine/export dual view makes it distinguishable from the plural get_strategies sibling 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 Guidelines3/5

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

Usage is implied rather than stated: it is the tool that resolves a strategy id into its rule set, and the note about deleted strategies hints at the case of chasing an old signal. There is no explicit 'use this when...' or 'use get_strategies instead when...' guidance in the description itself.

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.