quanttogo-mcp

check_subscription

Retrieve your subscription status and remaining trial days with your API key.

Instructions

Check subscription status and remaining trial days. Requires API key from register_trial.

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": {
      "apiKey": "<apiKey>"
    },
    "name": "check_subscription"
  }
}

Input Schema

Name	Required	Description	Default
`apiKey`	Yes	Your API key from register_trial (starts with 'qtg_')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Mar 12, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It reveals the tool checks status and remaining days and requires an API key, but does not disclose behavioral traits such as read-only nature, error handling, rate limits, or what happens with invalid keys.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with the purpose in the first sentence and a prerequisite in the second. No redundancy, efficient, and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool, the description is minimally adequate but lacks information about the return value or behavior (no output schema). The agent cannot infer what the response contains, which is a gap for a complete understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already describes the 'apiKey' parameter with detailed format hints (starts with 'qtg_'). The tool description reiterates the prerequisite but adds no new meaning beyond the schema, warranting the baseline score.

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?

Description clearly states it checks subscription status and remaining trial days, providing a specific verb and resource. However, it does not differentiate from the sibling tool 'get_subscription_info', which may have overlapping functionality.

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?

The description gives a clear prerequisite (requires API key from register_trial) but lacks guidance on when to use this tool versus alternatives or when not to use it. No explicit exclusions or comparisons are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server