getSubscriptionPlans
Read-only
List subscription plans.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
TgPay Merchant API
by com.tgpaybot
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint and destructiveHint annotations already declare this as a safe read operation. The description adds no behavioral context beyond the annotation, such as what is returned, whether archived plans are included, or any pagination or ordering behavior.
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?
The description is a single, concise sentence with no filler or redundant information. It is appropriately front-loaded and every word earns its place.
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?
Given the low complexity, zero parameters, and read-only annotations, a one-line description is mostly sufficient. However, without an output schema, the description does not clarify what details are returned or whether archived/inactive plans are included, leaving minor ambiguity.
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 has zero parameters and 100% schema description coverage, so there are no parameter semantics that the description needs to clarify. The baseline of 4 applies because no parameters exist.
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?
The description uses a specific verb ('List') and resource ('subscription plans'), making the core function immediately clear. It does not explicitly differentiate from sibling tools such as getSubscriptions or createSubscriptionPlan, so an agent must infer the distinction from the resource name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus alternatives, such as getSubscriptions for user-specific subscriptions or createSubscriptionPlan for creating plans. There is no mention of exclusions, prerequisites, or preferred context.
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.
TDQS
A3.5/5.0
Disambiguation5/5
Each tool maps to a distinct resource or action: invoices, subscription plans, subscriptions, checks, transfers, balance, rates, and auth flows. The two-step connect/connect_status pair is clearly separated into initiate and poll, and similar actions like archiveSubscriptionPlan versus cancelSubscription are explicitly differentiated.
Naming Consistency4/5
The vast majority of tools follow a camelCase verb_noun pattern such as createInvoice, getSubscriptions, and refundInvoice. The exceptions are connect_status and get_docs, which use snake_case, creating a minor but noticeable inconsistency.
Tool Count4/5
At 21 tools, the server is on the heavier side but the breadth of a merchant payment API justifies it: auth, invoices, subscriptions, transfers/checks, balances, exchange rates, stats, webhooks, and docs all need coverage. No tools feel redundant, though a few list-only endpoints could arguably be consolidated.
Completeness3/5
Core invoice and subscription lifecycles are well covered: create, list, delete, archive, cancel, and refund. However, there is no visible createTransfer or createCheck tool even though the API includes transfers/checks docs and deleteCheck/getTransfers, leaving a notable dead end for initiating transfers.