Skip to main content
Glama

Plan, limits and usage

get_plan_and_usage
Read-onlyIdempotent

The workspace plan, every limit it sets and what has been used this window (requests/min, posts and AI credits per month, brands, profiles, seats). Read this before telling a user they cannot do something — a 429 names the metric it refused; this names the reset time and the plan that would allow it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description adds that the data is window-scoped and includes reset time and the plan that would permit the blocked action, which is real context beyond the annotations. It omits any note on permissions or whether the read is workspace-scoped for a caller with multiple workspaces.

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?

The resource and its returned contents are front-loaded in the first sentence, and the parenthetical metric list replaces a paragraph. The second sentence is long but every clause adds actionable information about the 429 scenario.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining return values and does so by enumerating plan, limits, usage metrics and reset time. It is close to complete for a zero-parameter read tool, though it does not sketch the response shape or say what happens if no plan data is available.

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 no parameter semantics to document; baseline is 4. Nothing in the description misdescribes the calling contract.

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?

Names a specific resource (the workspace plan) and enumerates exactly what is returned: every limit plus current-window usage across named metrics (requests/min, posts, AI credits, brands, profiles, seats). This is precise enough to separate it from sibling list_plans, which implies plan enumeration rather than limits-plus-consumption.

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?

Gives an explicit trigger for use: read it before telling a user they cannot do something, especially after a 429, because this tool names the reset time and the plan tier that would lift the limit. It does not state when-not to use it or name an alternative tool, so it falls short of the 5 criteria.

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