Skip to main content
Glama

get_usage

Read-onlyIdempotent

Report the calling key's monthly quota state: tier, calendar month, renders used, monthly limit, remaining renders, and the date the count resets.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish the safe, read-only, idempotent, closed-world profile, so the description doesn't need to repeat those traits. It adds useful disclosure of what the report contains, including the reset date and remaining renders, which is valuable given there is no output schema. It stops short of mentioning error behavior or whether the response is cached, so 4 rather than 5.

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 description is a single sentence that front-loads the primary action and scope before listing the reported fields. Every clause earns its place: the field list is the only way the agent learns the response shape without an output schema.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does so completely by enumerating the quota fields and the reset date. Nothing an agent needs in order to call this tool correctly or interpret its result is missing.

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?

There are zero input parameters, which sets the baseline at 4. The description adds scope semantics by specifying that the quota reported is for the 'calling key,' which is implicit information an agent needs and cannot get from an empty 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?

The description opens with a specific verb and resource: 'Report the calling key's monthly quota state.' It then enumerates the exact fields returned (tier, calendar month, renders used, limit, remaining, reset date), which clearly distinguishes it from get_pricing and render_pdf.

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

Usage Guidelines3/5

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

The purpose implies usage—check the quota for the current calling key—and the sibling set makes the context obvious. However, the description never explicitly says when to choose this tool over get_pricing or when to call it relative to render_pdf, leaving that to inference.

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