Skip to main content
Glama

get_plan_usage

Read-onlyIdempotent

How much of the workspace's plan allowances are used, before anything is attempted: reel schedules, AI caption generations, trial reels and AI DM replies (each a rolling month), and active automations (at once).

limit null means unlimited and remaining null with it; limit 0 / included false means the plan does not include the feature at all. Call it before a big batch (schedule_reels_bulk, many captions) or when a tool answers with an upgrade message, so the user hears what is left now rather than from a failure. It reads counters only and claims nothing. Billing, invoices and changing plan are not available here — point the user to reeldrop's Billing page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>"
    },
    "name": "get_plan_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
noteYes
planYes
trial_reelsYes
ai_dm_repliesYes
reel_schedulesYes
active_automationsYes
caption_generationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that the call only reads counters and 'claims nothing', i.e. consumes no allowance, and explains the null/zero semantics of limits and included flags. It does not add much on auth or rate limits, but the side-effect profile is clearly reinforced rather than merely repeated.

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?

Front-loaded with purpose, then semantics, then usage triggers and exclusions — a logical order with no filler. The first sentence is dense with the feature enumeration, but each clause carries distinct information.

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?

An output schema exists, so return-shape explanation is not required, and the description still covers the interpretation of edge values, when to call, what side effects do not occur, and what the tool explicitly cannot do. Nothing an agent needs in order to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter (workspace_id) with 0% schema description coverage, and the description never explains it. The parameter is largely self-evident from the name and the surrounding context, but the description adds no meaning beyond the 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?

States a specific verb+resource: reports how much of the workspace's plan allowances are used, enumerated per feature (reel schedules, AI captions, trial reels, AI DM replies, active automations). It also draws a boundary against nearby concepts by stating billing/invoices/plan changes are not available here, so an agent can tell it apart from other account-facing siblings.

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?

Gives explicit triggering conditions: call before a big batch (naming schedule_reels_bulk and many captions) or when another tool returns an upgrade message. It also gives an explicit out-of-scope routing (Billing page for billing/invoices/plan changes), which is exactly the when-not guidance an agent needs.

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.

Resources