Skip to main content
Glama

Pay2GPT

List plans and prices

list_plans
Read-onlyIdempotent

List every Pay2GPT plan (ChatGPT Go, Plus, Pro, Codex credits and the rest) with its current price in US cents for each website payment method (card, alipay, crypto), whether it can be bought now, and its checkout URL. Card and Alipay include the card service fee; crypto pays the list price. Ruble methods are quoted at checkout.

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": "list_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description still adds genuine behavioral context the annotations cannot: card and Alipay prices include the card service fee, crypto pays list price, Ruble methods are only quoted at checkout, and the response includes an availability flag plus checkout URL. It stops short of noting freshness/caching of prices or that prices are static snapshots.

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 verb and resource, and the second sentence cleanly captures the pricing-fee caveat. The parenthetical plan enumeration ('ChatGPT Go, Plus, Pro, Codex credits and the rest') is illustrative but slightly padded; the sentence could be trimmed 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?

With no input parameters and no output schema, the description carries the full burden of describing the return payload, and it does so: per-method cent prices, purchasability, and checkout URL, plus the fee/currency caveats. Nothing an agent needs in order to call this correctly is missing.

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 zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The description correctly does not invent inputs, and instead spends its words on output semantics.

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 (List) and resource (Pay2GPT plans) and enumerates exactly what each entry carries: price in US cents per payment method, availability, and checkout URL. This is clearly distinct from the sibling list_* tools, which target articles and business orders rather than plans/prices.

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?

Usage is implied rather than stated: an agent can infer this is the catalog/pricing lookup, but there is no explicit 'use this when...' or 'use X instead when...' routing, and no mention of prerequisites such as authentication or whether an API key is needed. For a zero-argument listing tool the gap is small but real.

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