Skip to main content
Glama

Plan and billing

billing
Read-only

Check your Camberstack plan usage to compare Google Ads accounts and Free change allowances against plan limits, and access links to upgrade, change card, or cancel.

Instructions

Shows the user's Camberstack plan: the Google Ads accounts used in the last 30 days against the number the plan covers (Free 1, Plus 1, Pro 5, Agency 25), and on Free the applied changes used of those included. Returns personal links to upgrade (Free to Plus or Pro, Plus to Pro, Pro to Agency) or to change card and cancel (paid plans). This is the Camberstack subscription only, not a Google Ads account's own billing, invoices or ad spend.

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": "billing"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that, the description discloses the substantive behavior an agent needs: the return payload includes personal links to upgrade, change card, and cancel, plus quota usage numbers — useful because those links are actionable even though the call itself is a read. It stops short of mentioning auth prerequisites or what happens when no subscription exists.

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 definition is front-loaded with the resource and its contents, then the return links, then the scope exclusion — a sensible ordering. The first sentence is long and stacks the tier list parenthetically, which is dense but each clause (limits, applied changes) carries real information; little is wasted.

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 no input parameters and no output schema, the description carries the full burden and does so: it explains the quota comparison, the tier thresholds, the Free-only applied-changes metric, and the kinds of links returned. An agent can answer 'should I call this and what will I get' without opening anything else.

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 there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. No misleading parameter claims are made.

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 names a concrete verb and resource ('Shows the user's Camberstack plan') and enumerates exactly what is reported: Google Ads accounts used in the last 30 days versus the plan cap, per-tier limits (Free 1, Plus 1, Pro 5, Agency 25), and Free-tier applied changes. It also explicitly separates itself from a Google Ads account's own billing, invoices or ad spend, so an agent can distinguish it from spend-related siblings like merchant_ad_spend.

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?

The negative scoping sentence ('This is the Camberstack subscription only, not a Google Ads account's own billing, invoices or ad spend') gives a clear when-not-to-use rule for the most likely confusion. It also implies use for upgrade/downgrade/card-change questions by listing those links. However, it never states a positive trigger such as 'use when the user asks about plan limits or upgrading', so guidance is strong but not fully explicit.

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