Skip to main content
Glama

Read the strategy Python API

get_strategy_guide
Read-onlyIdempotent

Read Premiss's Python package format, the event strategy API (on_bar, on_schedule, on_fill and the other handlers), spot and perpetual modes, execution timing and examples. Custom indicators, entry/exit logic and risk rules use the same engine as the Premiss app.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
guideYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and determinism are fully covered by structured data. The description adds useful content scope by naming the handler set and the covered modes, but says nothing about response shape, size, or whether the guide is static documentation versus generated content. With annotations carrying the behavioral profile, a 3 is appropriate.

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?

It is a single dense sentence with the key resource front-loaded ('Read Premiss's Python package format, the event strategy API'), followed by supporting enumerations. The parenthetical handler list is slightly heavy but every element names real content, so nothing 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 no input parameters, an output schema present, and annotations covering safety and determinism, the description only needs to convey scope and it does so thoroughly. The one remaining gap is not stating how it relates to get_strategy, which an agent might reasonably consider as an alternative source of strategy information.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter meaning is lost because none exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Read') and enumerates the exact resource contents: the Python package format, the event strategy API with named handlers (on_bar, on_schedule, on_fill), spot/perpetual modes, execution timing and examples. This lets an agent distinguish it from get_strategy or create_strategy, though it never explicitly contrasts itself with those siblings.

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 only implied: an agent can infer this is the reference to consult when authoring custom indicators, entry/exit logic, or risk rules, since the description says those 'use the same engine as the Premiss app'. There is no explicit when-to-use statement, no when-not, and no named alternative such as get_strategy for existing strategy data.

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