Skip to main content
Glama

Usage and Quota

usage
Read-onlyIdempotent

Return the current account tier, per-tool-group usage, rate limits, and stateful Monitor and Strategy quotas.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
tierNoAccount tier.
toolsNoUsage and quota information grouped by tools that share a limit.
monitorNo
strategyNo
upgrade_hintNoOptional account-capacity information for tiers that have an upgrade path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "tier",
      -  "tools",
      -  "monitor",
      -  "strategy"
      -]
  2. Changed1 schema field changed
    • removedOutput schema / properties / tier / enum
      Removed value: -[
      -  "guest",
      -  "member",
      -  "lite",
      -  "premium",
      -  "platinum"
      -]
  3. Changed1 schema field changed
    • addedOutput schema / properties / tools / items / properties / cost_per_call
      Added value: +{
      +  "description": "Present when one call can use more than one unit of the daily limit; states how a call is counted.",
      +  "type": "string"
      +}
  4. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world call, so the safety profile is covered. The description adds that quota data spans Monitor and Strategy groups, which hints at cross-tool relevance, but says nothing about freshness, auth requirements, or how quotas are counted beyond what the output schema likely shows.

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?

A single front-loaded sentence with no filler. Every listed item is substantive and the structure moves from the account-level tier to the more specific quotas.

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?

For a no-argument tool with an output schema and full annotation coverage, the definition is essentially complete; the only real omission is guidance on when an agent should call it (for example, before exhausting rate limits).

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 of 4 applies; there is no parameter meaning the description needs to compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Return') and enumerates the resource contents: account tier, per-tool-group usage, rate limits, and Monitor/Strategy quotas. This clearly distinguishes it as a quota/introspection tool, though it never explicitly contrasts itself with siblings like monitor or strategy whose quotas it reports.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of using it to check remaining quota before calling other tools, and no exclusions. Usage is only inferable from the content list, not stated.

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.