Read plans, usage, subscription state, payment-method summary and invoices. Reconciles subscription state with Stripe; use invoice_cursor for older invoices.
| Name | Required | Description | Default |
|---|---|---|---|
| invoice_cursor | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Output schema / anyOfPrevious value: -[
- {
- "additionalProperties": {},
- "propertyNames": {
- "type": "string"
- },
- "type": "object"
- },
- {
- "additionalProperties": {},
- "properties": {
- "error": {
- "type": "string"
- },
- "message": {
- "type": "string"
- }
- },
- "required": [
- "error"
- ],
- "type": "object"
- },
- {
- "additionalProperties": {},
- "properties": {
- "message": {
- "type": "string"
- },
- "next_action": {
- "type": "string"
- },
- "operation_id": {
- "type": "string"
- },
- "status": {
- "type": "string"
- }
- },
- "required": [
- "operation_id",
- "status"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": {},
+ "properties": {
+ "available": {
+ "type": "boolean"
+ },
+ "entitlement": {
+ "additionalProperties": false,
+ "properties": {
+ "callBlocked": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "freeCalls": {
+ "type": "number"
+ },
+ "freeCallsLeft": {
+ "type": "number"
+ },
+ "freeCallsUsed": {
+ "type": "number"
+ },
+ "maxMinutesPerCall": {
+ "type": "number"
+ },
+ "nextPlan": {
+ "anyOf": [
+ {
+ "enum": [
+ "free",
+ "starter",
+ "pro",
+ "pro_starter",
+ "pro_plus",
+ "pro_max"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "period": {
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "end": {
+ "type": "string"
+ },
+ "start": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "start",
+ "end"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "plan": {
+ "enum": [
+ "free",
+ "starter",
+ "pro",
+ "pro_starter",
+ "pro_plus",
+ "pro_max"
+ ],
+ "type": "string"
+ },
+ "planChangesAt": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "planName": {
+ "type": "string"
+ },
+ "usageIncluded": {
+ "type": "number"
+ },
+ "usageLeft": {
+ "type": "number"
+ },
+ "usageLeftPct": {
+ "type": "number"
+ },
+ "usageUsed": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "plan",
+ "planName",
+ "freeCalls",
+ "freeCallsUsed",
+ "freeCallsLeft",
+ "usageIncluded",
+ "usageUsed",
+ "usageLeft",
+ "usageLeftPct",
+ "period",
+ "nextPlan",
+ "planChangesAt",
+ "maxMinutesPerCall",
+ "callBlocked"
+ ],
+ "type": "object"
+ },
+ "has_saved_payment_method": {
+ "type": "boolean"
+ },
+ "invoices": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "amount_due": {
+ "type": "number"
+ },
+ "amount_paid": {
+ "type": "number"
+ },
+ "currency": {
+ "type": "string"
+ },
+ "id": {
+ "maxLength": 200,
+ "minLength": 1,
+ "type": "string"
+ },
+ "pdf": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "url": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "id",
+ "status",
+ "amount_due",
+ "amount_paid",
+ "currency",
+ "url",
+ "pdf"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "next_cursor": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "operation_id": {
+ "type": "string"
+ },
+ "payment_method": {
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "brand": {
+ "type": "string"
+ },
+ "id": {
+ "maxLength": 200,
+ "minLength": 1,
+ "type": "string"
+ },
+ "last4": {
+ "type": "string"
+ },
+ "type": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "type"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "plan": {
+ "enum": [
+ "free",
+ "starter",
+ "pro",
+ "pro_starter",
+ "pro_plus",
+ "pro_max"
+ ],
+ "type": "string"
+ },
+ "plans": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "name": {
+ "type": "string"
+ },
+ "plan": {
+ "enum": [
+ "starter",
+ "pro",
+ "pro_starter",
+ "pro_plus",
+ "pro_max"
+ ],
+ "type": "string"
+ },
+ "priceCents": {
+ "type": "number"
+ },
+ "usageUnits": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "plan",
+ "name",
+ "priceCents",
+ "usageUnits"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "subscription": {
+ "additionalProperties": false,
+ "properties": {
+ "cancel_at_period_end": {
+ "type": "boolean"
+ },
+ "change": {
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "at": {
+ "type": "string"
+ },
+ "plan": {
+ "enum": [
+ "free",
+ "starter",
+ "pro",
+ "pro_starter",
+ "pro_plus",
+ "pro_max"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "plan",
+ "at"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "status": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "status",
+ "cancel_at_period_end",
+ "change"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "plan",
+ "plans",
+ "entitlement",
+ "subscription",
+ "has_saved_payment_method",
+ "payment_method",
+ "invoices",
+ "next_cursor",
+ "available"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": {},
+ "properties": {
+ "error": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "error"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": {},
+ "properties": {
+ "message": {
+ "type": "string"
+ },
+ "next_action": {
+ "type": "string"
+ },
+ "operation_id": {
+ "type": "string"
+ },
+ "status": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "operation_id",
+ "status"
+ ],
+ "type": "object"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description adds value by disclosing that the tool reconciles subscription state with Stripe—an external side effect that matters despite read-only semantics. It does not mention auth requirements or rate limits, but the external reconciliation disclosure is meaningful context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tightly written sentences. The resource list is front-loaded, and the behavioral and parameter guidance follows without filler. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With annotations covering safety traits, an output schema documenting return values, and only one parameter whose purpose is explained, the description provides everything an agent needs to select and invoke this tool correctly. The Stripe reconciliation note covers the main non-obvious behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the single parameter (invoice_cursor) is only constrained by type and length in the schema. The description compensates by explaining that invoice_cursor is used for older invoices, giving the parameter practical meaning. It does not specify the cursor format, but the opaque nature of cursors makes that omission acceptable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Read') and enumerates the exact resources covered: plans, usage, subscription state, payment-method summary, and invoices. It is clearly distinguishable from sibling mutation tools like update_billing_profile, though it does not explicitly name an alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It provides clear context for when to use the tool (reading billing information) and explicitly explains the invoice_cursor parameter's role for older invoices. It does not state when not to use it or name a specific alternative sibling, which keeps it below a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.