Skip to main content
Glama

Get plan usage

get_usage
Read-only

Shows the account plan, paid live transactions used and remaining this period, and the period end date. Use it to check plan quota; test payments are excluded.

Instructions

Shows the account's plan, its paid transactions used and left this period, and when the period ends. Only paid live payments count; test payments never do.

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 observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine interpretive context beyond them: the counting semantics that test payments are excluded and only paid live payments count, which directly affects how an agent reads the returned numbers. It says nothing about auth requirements or error behavior, but that gap is small for a read-only status call.

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 sentences with zero waste: the payload is front-loaded and the qualifying rule follows as a short caveat. Every clause carries information an agent would otherwise have to guess.

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 input parameters and no output schema, the description must carry the return-value burden alone, and it does: it names the three returned quantities and the period boundary. For a simple read-only status tool this is complete enough to call and interpret correctly.

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 and the schema is empty at 100% coverage, so there is nothing for the description to disambiguate. Baseline for a parameterless tool applies, with the implicit signal that the call is scoped to the authenticated account's current period.

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 (shows) and a specific resource (the account's plan usage), then enumerates the exact contents returned: plan, paid transactions used and left this period, and period end. The counting rule ('only paid live payments count; test payments never do') further separates it from the test-payment siblings in substance, so an agent can pick it without opening a schema.

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?

There is no explicit when-to-use statement or named alternative (e.g. 'use this for billing questions, use list_payments for individual transactions'). Usage is only implied by the described contents, which is adequate for an obvious zero-parameter account-status read but leaves the agent to infer the trigger conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.