Skip to main content
Glama

Get Strategy List by Id

tt_get_list
Read-onlyIdempotent

Reverse-resolve a numeric list_id to its list metadata (name, segment, exchange, instrument_count).

Use when a fetched strategy carries list: <id> and you need the list's NAME — e.g. to render it for the user, or to author the |<LIST NAME>| pipe token in a condition (the token must be the exact name). Best-effort over the signed-in user's visible lists (own + public); resolved: false means the id wasn't found there.

AUTH-REQUIRED: returns the connect funnel when no Tradetron account is connected.

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": {
      "list_id": "<list_id>"
    },
    "name": "tt_get_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, and the description adds genuinely new context: visibility scope (own + public lists), best-effort failure signaled by `resolved: false`, and an auth-required connect funnel when no account is connected. That exceeds the annotation bar, though it doesn't cover error shapes beyond the not-found case.

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-loads the purpose, then usage, then scope and failure modes and auth, in three short paragraphs. Efficient and skimmable, with only mild overlap between the metadata field list and the later emphasis on NAME.

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?

For a single-parameter lookup with no output schema, the description supplies enough to call and interpret it: the resolved metadata fields, the `resolved: false` not-found contract, visibility limits, and the auth failure mode.

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% with one required integer, so the description must compensate. It does by clarifying that list_id is numeric, where such ids come from (a strategy's `list` field), and that resolution is limited to the signed-in user's visible lists — meaning ids outside that set will legitimately fail.

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: 'Reverse-resolve a numeric list_id to its list metadata', and names the return fields (name, segment, exchange, instrument_count). This is clearly distinguishable from the many tt_get_strategy*/tt_list_* siblings because it resolves an id rather than fetching a strategy or enumerating lists.

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?

Gives concrete when-to-use triggers: when a strategy carries `list: <id>` and you need the name to render it or to author the `|<LIST NAME>|` pipe token. It does not name an alternative tool or state when not to call it, so it falls short of the top tier.

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