Skip to main content
Glama

subscription

subscription
Read-only

Recurring tier: a PREPAID CALL BALANCE. One x402 payment of $1.00 credits 1,000 units of prepaid capacity (= $0.0010 per call), drawn down across sessions on the cheap deterministic routes (<= $0.01). The funded balance is the source of truth, queryable at GET /v1/subscription/balance, and remaining_calls is reported on every paid response. Non-auto-renewing: a one-time top-up whose spend stops at zero. No account, no API key, no monthly lock-in. $1.00 USDC per successful call (x402, client-paid); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior3/5

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

The description adds useful behavioral context beyond the read-only annotations: prepaid drawdown, non-auto-renewing top-up, no account/API key, and failed calls not charged. However, it contains potentially confusing internal inconsistencies, such as 'Recurring tier' paired with 'Non-auto-renewing' and '$0.0010 per call' alongside '$1.00 USDC per successful call,' which reduces transparency about cost behavior.

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

Conciseness2/5

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

The description is overly long for a zero-parameter tool and repeats pricing/cost information in multiple forms. The duplicated and sometimes inconsistent cost statements make it less efficient and harder to parse.

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

Completeness2/5

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

With no output schema, the description should clarify what the tool returns, but it mainly describes the subscription plan and external balance endpoint. It does not explicitly connect the tool invocation to a return value, leaving the agent without a clear model of the response.

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, so the baseline is 4. The empty input schema means there are no parameter semantics for the description to clarify.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explains what the subscription tier is (a prepaid call balance) but never states what invoking this tool actually does or returns. There is no clear verb+resource action such as 'retrieves subscription status' or 'returns remaining balance,' and it does not differentiate itself from the batch/validation siblings.

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?

It provides no explicit guidance on when to use this tool versus alternatives. The closest signal is that the funded balance is 'queryable at GET /v1/subscription/balance,' but that is a plan detail rather than an instruction for tool selection.

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.