Skip to main content
Glama

Get quota usage

get-quota-usage
Read-only

Get used, limit and remaining for each quota: quotaPrompts (active prompts), quotaArticles (this billing period), quotaSiteAudits and quotaChat. A null limit means unlimited. get-account-info returns the subscription.

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-quota-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=true and destructiveHint=false, so the description only needs to add semantic context — which it does by defining that a null limit means unlimited and that quotaArticles is scoped to the current billing period. It does not describe response shape or whether quota values can be stale/lagging, leaving a small gap.

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?

Two short sentences front-loaded with the core action and field list, plus one routing sentence. Nothing is redundant or buried.

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 describing returns, and it largely does: used, limit, remaining, the four quota keys, and the null-means-unlimited convention. It omits units/format of the numeric values and any error or auth behavior, but an agent has enough to call and interpret the result.

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 the baseline is 4. The description's per-quota naming and the null-limit rule add genuine meaning about the returned fields, which is the useful analogue of parameter semantics for a no-arg tool.

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 (get quota usage) and enumerates exactly which quotas are reported (quotaPrompts, quotaArticles, quotaSiteAudits, quotaChat), including the scope of each ('active prompts', 'this billing period'). It also distinguishes itself from get-account-info, so an agent can pick between them without opening either schema.

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 closing sentence routes subscription questions to get-account-info, which is an explicit alternative and implies this tool is for quota consumption only. It stops short of stating when-not to call it or any preconditions, so it is clear context rather than full when/when-not guidance.

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