Skip to main content
Glama

My Subscription

tt_get_my_subscription
Read-onlyIdempotent

The signed-in user's current plan, renewal date, usage, and a usage-grounded upgrade recommendation.

AUTH-REQUIRED: if the user hasn't connected their Tradetron account, this returns an auth-required funnel (connect link + signup link + guidance) — relay it warmly; do NOT invent subscription details. Use for "what's my plan?", "when does my subscription expire?", "should I upgrade?". The recommendation only fires on a real binding limit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 already declare readOnly, idempotent, non-destructive, closed-world, so the bar is met; the description then adds behavior annotations cannot express: an AUTH-REQUIRED path that returns a connect/signup funnel, an instruction not to fabricate subscription details, and the caveat that the recommendation only fires on a real binding limit. That is material context for interpreting an empty-looking response.

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?

The return contents are front-loaded in the first sentence, followed by the auth caveat and usage triggers in priority order. The line-wrapping is slightly ragged and the auth block could be tightened, but no sentence is filler.

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, and the description compensates by listing the returned fields explicitly. For a zero-parameter read tool, the remaining unknowns are covered by the auth-funnel explanation and the recommendation caveat, so an agent has enough to call and interpret 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?

The tool takes no parameters, so the baseline of 4 applies and there is no semantic gap for the description to fill. The schema coverage is 100% with an empty properties object, so nothing is undocumented.

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?

The description names a concrete verb-and-resource (the signed-in user's subscription) and enumerates exactly what comes back: current plan, renewal date, usage, and an upgrade recommendation. That distinguishes it from adjacent account tools such as tt_get_my_profile or tt_get_my_brokers without the agent needing to open a schema.

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?

It gives explicit trigger phrasings — "what's my plan?", "when does my subscription expire?", "should I upgrade?" — so the agent knows when to select it. It stops short of naming a when-not condition or an alternative tool, but the sibling set covers different resources, so the routing risk is low.

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