Proof Holdings

get_subscription

Read-only

Get the current subscription details including plan, status, billing period, and usage limits.

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open this tool.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`plan`	Yes	Plan to check out. `free` adds a card for pay as you go (the metered price past the included proofs); it is offered once billing is live.
`status`	Yes	Stripe's status for the subscription, whatever it is (the caller decides what counts as subscribed); null when the account has no subscription.
`scheduled_plan`	No	The plan a scheduled downgrade moves the account to at `scheduled_change_at`; null when nothing is scheduled. Absent from an API that predates plan changes.
`current_period_end`	Yes	End of the current billing period; null without a subscription.
`scheduled_change_at`	No	When the scheduled downgrade takes effect (the end of the paid period); null when nothing is scheduled.
`cancel_at_period_end`	Yes	Whether the subscription ends at the end of the current period; false without a subscription.
`current_period_start`	Yes	Start of the current billing period; null without a subscription.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "The account's subscription",
+  "properties": {
+    "cancel_at_period_end": {
+      "description": "Whether the subscription ends at the end of the current period; false without a subscription.",
+      "type": "boolean"
+    },
+    "current_period_end": {
+      "description": "End of the current billing period; null without a subscription.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "current_period_start": {
+      "description": "Start of the current billing period; null without a subscription.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "plan": {
+      "description": "Plan to check out. `free` adds a card for pay as you go (the metered price past the included proofs); it is offered once billing is live.",
+      "type": "string"
+    },
+    "scheduled_change_at": {
+      "description": "When the scheduled downgrade takes effect (the end of the paid period); null when nothing is scheduled.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "scheduled_plan": {
+      "description": "The plan a scheduled downgrade moves the account to at `scheduled_change_at`; null when nothing is scheduled. Absent from an API that predates plan changes.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "description": "Stripe's status for the subscription, whatever it is (the caller decides what counts as subscribed); null when the account has no subscription.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "plan",
+    "status",
+    "current_period_start",
+    "current_period_end",
+    "cancel_at_period_end"
+  ],
+  "type": "object"
+}

First observedSep 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real value beyond that by disclosing the authentication requirement and the failure mode (call this tool again after authenticating), which an agent would otherwise hit blindly.

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 purpose sentence, then a clearly labeled ACCESS block. Slightly verbose for the auth instructions, but every sentence carries actionable information and nothing is redundant.

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

Completeness4/5

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

An output schema exists, so return values need not be described. The two things an agent actually needs — what it returns conceptually and the auth gate — are both present, leaving no significant gap for this simple read tool.

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 to disambiguate; the baseline for an empty schema is 4. The description correctly implies no input is needed.

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?

States a specific verb ('Get') and resource ('current subscription details') and enumerates the returned fields: plan, status, billing period, usage limits. It is distinguishable from siblings like get_usage or get_balance by the subscription framing, though it never explicitly contrasts with them.

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?

Provides a prerequisite context (a Proof account, authenticate the client, and the note that start_login does NOT open this tool), which is genuine usage guidance. However, it gives no guidance on when to prefer this over adjacent reads such as get_usage, get_settings, or get_platform_summary.

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

All Proof Holdings tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.