Skip to main content
Glama

Manawa Terminal

Get strategy

get_strategy
Read-only

Read one strategy's current or historical generation (markdown, settings, links).

The playbook text is returned in full. It is not cut at the usual response size.

Args:
    strategy_id: Strategy UUID from list_strategies
    generation: Optional GCS generation for an older save (from list_strategy_versions)

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": {
      "strategy_id": "<strategy_id>"
    },
    "name": "get_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
generationNo
strategy_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: the playbook text is returned in full and is not truncated at the usual response size, which affects how an agent should consume the result.

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 caveat, with no filler. The second sentence ('It is not cut at the usual response size') restates the first slightly, but it reinforces an important operational fact rather than adding noise.

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?

An output schema exists so return-shape explanation isn't needed, both parameters are semantically documented, and the truncation caveat covers the main behavioral surprise. Nothing an agent needs to invoke this 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%, so the description must carry the load, and it does: strategy_id is a UUID sourced from list_strategies, and generation is an optional GCS generation pointer from list_strategy_versions for older saves. Both parameters gain meaning beyond their bare string types.

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 (read), singular resource (one strategy), and scope (current or historical generation), plus what content is included (markdown, settings, links). This clearly separates it from list_strategies and list_strategy_versions in the sibling set.

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

Usage Guidelines4/5

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

Names where each ID comes from — strategy_id from list_strategies, generation from list_strategy_versions — which implicitly routes the agent to the right sibling before calling. It doesn't explicitly state when to prefer this over list_strategies, but the singular-scope framing makes the distinction reasonably clear.

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