agentcard

get_plan

Read-onlyIdempotent

Show the user's current subscription plan, card limits, and this month's usage. Call this before create_card when you need the per-card amount cap or remaining monthly quota, or whenever the user asks about their plan, limits, billing, or upgrading. To cancel a paid plan, the gated tool cancel_plan also exists; call it by name even though it isn't in the tools list.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`plan`	No	Raw plan id, e.g. 'free', 'basic', or 'pro'.
`message`	Yes	Human-readable plan + usage summary.
`planName`	No	Display label of the plan, e.g. "Basic ($15/mo)".
`ordersPlaced`	No	Orders placed (counts toward the free-order quota on Free).
`cardsRemaining`	No	Cards remaining this month; null means unlimited.
`cardsThisMonth`	No	Number of cards created this month.
`currentPeriodEnd`	No	ISO date the current billing period ends, or null.
`maxCardsPerMonth`	No	Max cards allowed per month; null means unlimited (connections through a company OAuth client or organization have no card limits).
`cancelAtPeriodEnd`	No	Whether the subscription cancels at the end of the current billing period.
`maxLifetimeOrders`	No	Lifetime free-order quota; null means unlimited (paid plans).
`maxCardAmountCents`	No	Maximum funding per card, in cents; null means no per-card cap.
`subscriptionStatus`	No	Stripe subscription status (e.g. 'active', 'past_due'), or null on Free / when unavailable.
`maxCardAmountDollars`	No	Maximum funding per card, formatted as USD dollars, e.g. "500.00"; null means no per-card cap.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 28, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds context about the specific data returned (plan, limits, usage), which is useful but not 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.

Conciseness5/5

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

Two sentences, front-loaded with purpose, every sentence provides value. No wasted words.

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?

For a tool with no parameters and an existing output schema, the description fully explains what it does, when to use it, and what it returns. Complete.

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?

No parameters so baseline is 4. Description does not need to add param info.

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

Purpose5/5

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

The description clearly states the tool shows the user's current subscription plan, card limits, and monthly usage, using specific verbs and resources. It distinguishes itself from siblings like cancel_plan.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to call before create_card for per-card amount cap or remaining quota, and for user queries about plan, limits, billing, or upgrading. Also mentions cancel_plan as an alternative for cancellation.

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

All agentcard tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, especially in areas like card management and shopping. However, the KYC flow has multiple overlapping tools (start_kyc, get_kyc_status, check_kyc_document, submit_kyc_document, submit_kyc_fields) that could confuse an agent despite detailed descriptions.

Naming Consistency4/5

Tool names consistently use snake_case with a verb_noun pattern (e.g., add_funds, create_card, list_cards). A few exceptions like surprise_me and whoami break the pattern but are still intuitive overall.

Tool Count3/5

50 tools is on the high side for a single server, but the broad domain (cards, shopping, KYC, support, settings) partially justifies it. Some tools could be merged (e.g., KYC flow tools) without losing clarity.

Completeness4/5

The tool surface covers core workflows: CRUD for cards, transactions, KYC, support, shopping, and account management. Minor gaps exist (e.g., no update_card general, no cancel order in shopping), but overall the set is comprehensive for the stated purpose.

Resources

Need Help?