Skip to main content
Glama
Sign In
@proof-holdings/mcp-server

@proof-holdings/mcp-server

Official
by ProofHoldings
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_subscription

Read-only

Retrieves current subscription details, including plan, status, billing period, and usage limits, to help you review entitlements and monitor usage. Requires a Proof account and PROOF_API_KEY.

Instructions

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

ACCESS: needs a Proof account. Set PROOF_API_KEY and restart this server, then call this tool again. start_login does NOT open this tool.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
planYesPlan 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.
statusYesStripe's status for the subscription, whatever it is (the caller decides what counts as subscribed); null when the account has no subscription.
scheduled_planNoThe 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_endYesEnd of the current billing period; null without a subscription.
scheduled_change_atNoWhen the scheduled downgrade takes effect (the end of the paid period); null when nothing is scheduled.
cancel_at_period_endYesWhether the subscription ends at the end of the current period; false without a subscription.
current_period_startYesStart of the current billing period; null without a subscription.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.2
    • 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"
+}
  2. First observedv1.1.0

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 needs no restating. The description instead adds real behavioral context the annotations do not carry: the tool requires an authenticated Proof account via PROOF_API_KEY, needs a server restart to pick it up, and is explicitly NOT unlocked by start_login — a non-obvious failure mode worth flagging.

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?

The purpose sentence comes first and is followed by a clearly separated ACCESS block, so the structure is easy to scan. The access block is slightly verbose ('then call this tool again'), but each clause carries actionable information rather than filler.

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?

For a parameterless read tool with an output schema, the description covers purpose and the authentication prerequisite, which is the main thing that can go wrong. The only real gap is lacking differentiation from sibling usage/balance tools, a minor omission for something this simple.

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 at the input level. Mentioning plan, status, billing period, and usage limits describes the response shape rather than parameters, which is mild redundancy given an output schema exists.

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 names a specific verb and resource ('Get the current subscription') and enumerates the returned fields: plan, status, billing period, usage limits. It does not distinguish this from closely related siblings such as get_usage, get_balance, or get_platform_summary, so an agent must infer the boundary itself.

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?

It gives a clear prerequisite for calling the tool (a Proof account plus PROOF_API_KEY set and a server restart) and explicitly rules out start_login as a way to unlock it. What it never states is when to reach for this tool instead of get_usage or get_balance, which cover overlapping billing/usage territory.

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

Deploy Server

Other Tools