Skip to main content
Glama

Account: Get Plan Benefits & AI Credits

get_plan_and_credits
Read-onlyIdempotent

[Subscribe/Credits] [What it does] Reads the current account's subscription plan, plan limits/benefits, and current AI Credits balance in one call. [When to use] Use when the user asks about their current plan, what the plan includes, or their remaining AI Credits. Trigger words: my plan, plan benefits, Credits balance. [When not to use] For identity or permissions, use get_account_profile. For billing history or invoices, use get_plan_and_credit_billing. This tool returns no usage history or billing line items. [How to use] No inputs are required; call with an empty object. benefits are plan allowances and feature switches, not current usage. credit_balance has subscription_credits, lifetime_credits, and an authoritative total_credits; never sum the first two to replace it. current_subscription is only the current snapshot, not full subscription history. All required upstream reads must succeed together; if any fails, the whole call returns a retryable error instead of partial data. [Side effects] None; read-only. [Confirmation] Not required.

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_plan_and_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
benefitsYesLimits and feature entitlements included in the effective current subscription; these are allowances, not current usage
credit_balanceYesCurrent AI Credits balance split by subscription and lifetime buckets
active_subscriptionsYesAll currently effective DSers plans returned by Plan BFF: the recurring subscription first, followed by every active one-time Advanced, Pro, or Enterprise plan; an empty list is valid
current_subscriptionYesEffective current DSers subscription returned by the Plan endpoint; use active_subscriptions to distinguish the recurring plan from active one-time plans
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered; the description still adds real behavior beyond them — an all-or-nothing read where any failed upstream dependency produces a retryable error instead of partial data. The side-effects and confirmation lines largely restate the annotations, which keeps this from a 5.

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?

Bracketed section labels make it scannable and the core purpose is front-loaded before any caveats. The trigger-word list and the explicit confirmation line are mild redundancy, but nothing is padded or buried.

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 zero inputs, full annotation coverage, and an output schema, the description covers everything an agent needs: purpose, routing alternatives, empty-object invocation, field-semantics pitfalls, and the all-or-nothing failure mode. Nothing material is missing.

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?

Zero parameters, so the baseline is 4; the description correctly instructs calling with an empty object. It also pre-empts the main return-value misuse by clarifying that subscription_credits and lifetime_credits must not be summed in place of the authoritative total_credits, and that benefits are allowances rather than usage — meaning that adds value even though an output schema exists.

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?

States a specific verb and resource — reads the account's subscription plan, plan limits/benefits, and AI Credits balance in one call — and explicitly distinguishes itself from get_account_profile (identity/permissions) and get_plan_and_credit_billing (billing history). An agent can route between the three without opening a schema.

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?

Provides an explicit when-to-use section with trigger phrases (my plan, plan benefits, Credits balance), an explicit when-not-to-use section naming two concrete alternatives with their domains, and a negative statement that this tool returns no usage history or billing line items. This is the full when/when-not/alternatives triad.

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.