Skip to main content
Glama

My Strategy Subscriptions

tt_get_my_strategy_subscriptions
Read-onlyIdempotent

The signed-in user's marketplace strategy subscriptions — the whole history, not only the current ones — with their start/renewal/expiry dates.

status filters case-insensitively ("active" for the live ones), limit/offset page the rows: the first 25 by default, active rows first; summary.has_more / next_offset say when there are more. The summary counts always describe the WHOLE history, before any filter or page.

Every row carries a status. Compare it case-insensitively (the field is not normalised) and treat the value set as open-ended; only rows reading active are live subscriptions. TT defines no meaning for any other value, and rows read "upcoming" or "pending" on windows that closed months ago — trust a row's derived block over its status word. Rows whose derived.record_shape is set have no expiry, no amount and no currency: they are not dated paid subscriptions, so quote neither a renewal date nor a price for them. Rows can also arrive with no strategy_id — those are not marketplace strategy subscriptions (for the platform plan use tt_get_my_subscription). Read the counts off the response's summary block; never report the row count as the number of active subscriptions.

AUTH-REQUIRED (returns the connect/sign-up funnel if not authenticated).

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_get_my_strategy_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, 1 or more. Default 25 (active rows first); page on with offset. 0 is refused.
offsetNoRows to skip. Default 0.
statusNoFilter by status, case-insensitively — 'active' for the live ones. Omit for the whole history.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the safety profile (read-only, idempotent, non-destructive, closed-world); the description goes well beyond that by disclosing that summary counts span the whole unfiltered history, that the status field is un-normalised with an open-ended value set, that 'derived' overrides the status word, that record_shape rows have no expiry/amount/currency, that some rows lack strategy_id, and that unauthenticated calls return a connect funnel. These are exactly the traps an agent would otherwise fall into.

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 purpose and the single most important scope fact, then organised into parameter behaviour, row semantics, and auth. It is dense and every caveat targets a real failure mode, though the row-status paragraph is long enough that it could be tightened without losing meaning.

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?

There is no output schema, so the description carries the burden of describing the response — and it does: row fields (status, derived.record_shape, strategy_id, renewal/expiry dates), the summary block, and has_more/next_offset pagination. Combined with the auth note, an agent has everything needed to call it and interpret the result 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 100%, so the baseline is 3; the description still adds value by explaining the interaction between parameters and output — that the status filter is case-insensitive, that the default page is 25 with active rows first, and, importantly, that filtering or paging does not change the summary counts. That last point is semantics the schema cannot express.

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 and resource ('The signed-in user's marketplace strategy subscriptions') plus the crucial scope distinction that it returns the whole history, not just current ones. It also names the sibling to use for the platform plan (tt_get_my_subscription), so an agent can separate it from the near-identically-named alternatives.

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 clear operating context: how to get only live subscriptions ('active'), how to page, and an explicit routing rule away from tt_get_my_subscription for platform-plan rows. It also flags the auth requirement. What it lacks is a positive statement of when to prefer this over tt_get_my_deployed_strategies or tt_list_my_strategies, but the guidance it does give is actionable.

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