Skip to main content
Glama

Get plan and credits

get_plan_and_credits
Read-onlyIdempotent

Show the workspace's billing plan, its credit balance, what one approved brief costs in credits, and the plan limits (domains, questions, AI engines, monthly AI checks). Use it before a tool that spends credits or a plan allowance. A plan of 'free_trial' means the 3-day free trial: trial limits apply, and articles written in it carry a watermark and publish once the plan starts. A plan of 'paused' means the workspace has no active plan: it never started one, its trial or subscription was canceled, its billing is paused, or it took the 14-day money-back guarantee. Nothing is deleted, but checks and writing stay stopped until the workspace has an active plan again. Every plan has a 14-day money-back guarantee from the first payment, once per customer, refunded from the Billing page. pricing_url describes the plans.

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
planYes
limitsYes
creditsYes
billing_urlNo
pricing_urlNo
trial_ends_atNo
agency_billingNo
can_publish_to_cmsNo
current_period_endNo
brief_draft_cost_creditsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Despite readOnlyHint=true, idempotentHint=true, and destructiveHint=false already covering the safety profile, the description adds substantial behavioral context: what 'free_trial' and 'paused' mean, trial limits and watermarking behavior, that paused checks and writing stay stopped, that nothing is deleted, and how the 14-day money-back guarantee works. This is well beyond what the annotations supply.

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 first sentence front-loads what is returned, followed by a usage cue and then state-specific details. The content is dense but mostly earns its place, though the trial/paused/money-back explanation is longer than strictly necessary for tool selection.

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 an output schema present and no parameters, the description need not explain return shape. It nonetheless provides enough context about plan states, usage timing, limits, and pricing_url to make the tool's role unambiguous.

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 has zero parameters, so there are no parameter semantics to explain; baseline for zero parameters is 4. The description correctly does not waste space re-describing an empty input schema.

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 opens with a specific verb and enumerates the exact resources returned: billing plan, credit balance, approved-brief credit cost, and plan limits (domains, questions, AI engines, monthly AI checks). This distinguishes it clearly from sibling tools such as get_workspace and get_autopilot, which cover different workspace resources.

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

Usage Guidelines4/5

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

It explicitly says to use the tool before a tool that spends credits or a plan allowance, giving a clear trigger condition. It does not name alternatives or exclusions, but the usage context is direct enough that an agent can decide when to call it.

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.