Skip to main content
Glama

My Strategies

tt_list_my_strategies
Read-onlyIdempotent

The signed-in user's own SAVED strategy templates — id, name, edit_url — newest-updated first. AUTH-REQUIRED (returns the connect funnel if not authenticated).

THE name→id resolver: when the user refers to a strategy by NAME ("backtest CASH ON Nifty new", "edit my straddle"), call this with q= instead of asking them to fetch the template id or edit URL from the website. Covers ALL their templates, deployed or not (tt_get_my_deployed_strategies only lists deployed ones).

Args: q: optional case-insensitive substring of the strategy name. limit: rows to return (default 50, max 200). offset: rows to skip; the result's total is the filtered count.

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

Input Schema

NameRequiredDescriptionDefault
qNo
limitNoRows to return, 1..200. Default 50. A larger value is clamped to 200; below the minimum is refused.
offsetNoRows to skip. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses AUTH-REQUIRED behavior and what happens when unauthenticated (the connect funnel is returned instead of data), the default sort order, and the deployment-independent scope. What it does not cover is result-size/pagination behavior on the response side, which is a minor gap for a list tool.

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 the resource and the key resolver rule, then a compact Args block; the user-utterance examples earn their space by anchoring the q usage. Minor waste in restating limit/offset defaults and ranges already present in the schema.

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, the description still characterizes the return payload (id, name, edit_url, total) and ordering. Auth requirements, scope relative to the deployed-only sibling, and all three parameters are accounted for, so an agent has everything needed to call it correctly.

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 67% and the undocumented parameter (q) is exactly where the description adds value: case-insensitive substring match on strategy name. It also clarifies that the returned `total` is the filtered count, which the schema does not say. The limit/offset restatements largely duplicate the schema's own descriptions.

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+resource (list the signed-in user's SAVED strategy templates) and even enumerates the returned fields (id, name, edit_url) and sort order (newest-updated first). It explicitly distinguishes itself from the sibling tt_get_my_deployed_strategies by noting it covers deployed AND non-deployed templates.

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?

Gives a concrete when-to-use rule — act as the name→id resolver when the user names a strategy ("backtest CASH ON Nifty new", "edit my straddle") — including the anti-pattern to avoid (asking the user to fetch an id or edit URL from the website). It also names the alternative sibling and the condition that selects it.

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