Skip to main content
Glama

Read usage

usage
Read-onlyIdempotent

Units used and left (an account with no subscription is on the free plan, counted by the calendar month), when they reset, and every limit. Every key of the account draws on the same units. Free plan: 50 units a month, no card needed, for a signed-in person whose email address is confirmed. Queued renders need the subscription. We limit free plans to prevent abuse. Costs nothing.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {},
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish a safe, idempotent read, so the description's job is to add context, and it does: units are shared across every key on the account, the free plan meter runs by calendar month, queued renders require a subscription, and the call is free. That is genuine behavioral detail beyond the annotations. It stops short of describing response shape, but an output schema exists, so that omission is minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core answer is front-loaded, but the tail drifts into plan marketing ('no card needed', 'We limit free plans to prevent abuse', 'Costs nothing') that adds little to tool selection. The parenthetical about the free plan is also dense and slightly interrupts the main clause.

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 read tool with an output schema and safe annotations, the description supplies the account-level billing context an agent needs to interpret the numbers. The remaining gap is the relationship to the 'subscription' sibling, which is left unaddressed.

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 nothing for the description to disambiguate and the schema is fully covered. A baseline 4 is appropriate; no parameter guidance is needed or missing.

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 opening sentence names the specific resource returned: units used, units remaining, reset time, and every limit. That is concrete and agent-actionable. It does not distinguish itself from the sibling 'subscription' tool, which is the main gap.

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 explicit statement of when to call this rather than 'subscription', or of any prerequisite. The plan details imply a 'check consumption before rendering' use case, but the agent must infer it, and the overlapping sibling is never addressed.

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