Skip to main content
Glama

Read the plan

subscription
Read-onlyIdempotent

The account's plan: its status, period and whether it renews, and where its person manages it. Subscribe for $20 a month: 1,500 units a month and queued renders, on one account with as many API keys as you need. It renews automatically until cancelled; cancel any time. A person subscribes, starts the free plan, makes keys and cancels on the website (/engines/subscribe, /account/engines); no tool buys anything. Costs nothing.

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties / pass_quote
      Removed value: -{
      -  "description": "What the next pass costs this account, and why."
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "pass_quote": {
      +      "description": "What the next pass costs this account, and why."
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so silence on safety is fine; instead the description adds genuinely new behavior: auto-renewal until cancelled, cancellation being possible at any time, and all billing mutations living at /engines/subscribe and /account/engines. That clarifies the boundary between what this tool can and cannot change. It does not describe pagination or error modes, and for a zero-param read that is a minor omission.

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

Conciseness3/5

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

The first sentence is front-loaded and operational, and the website-routing sentence earns its place. But the middle pitch — '$20 a month: 1,500 units a month and queued renders, on one account with as many API keys as you need' — reads as marketing copy an agent does not need in order to read plan status, and it dilutes the signal.

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 parameters and an output schema already covering return values, the description only needs to establish what the plan object is and who may change it — both are covered. The explicit note that no tool can purchase or cancel closes the one ambiguity an agent might otherwise chase through siblings.

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 there is nothing for the description to disambiguate; per the rubric this is a baseline 4. The description wastes no effort inventing parameter meaning and correctly focuses on what the call returns.

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 opening sentence names the resource and the exact fields returned: plan status, billing period, renewal flag, and where the plan is managed. That is far more specific than the bare name 'subscription', and an agent can tell it reads account billing state rather than anything else. It stops short of naming a sibling to distinguish from, so it lands at 4 rather than 5.

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 supplies an explicit exclusion — 'no tool buys anything' and 'A person subscribes... cancels on the website' — telling the agent not to attempt purchase or cancellation through any tool. It also states 'Costs nothing', implying a safe free call. It does not address when to prefer it over cost-related siblings (material_cost, pull_cost), so 4.

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