Skip to main content
Glama

get_usage

Read the caller's verification usage overview over the default window: verdict breakdown, per-check usage, totals, and only the non-zero days of the activity series. Use it to see how many verifications ran and with which verdicts; for the token balance use check_balance, and for individual token movements use list_transactions. Requires the usage:read scope.

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.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: the data is scoped to the caller, uses a "default window," requires the usage:read scope, and the activity series is filtered to non-zero days only. It does not state whether the window is configurable or how large the payload can get, which keeps it short of a 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?

Three tight sentences: return contents first, then disambiguation from siblings, then the authorization prerequisite. Every clause carries information and there is no filler.

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?

No output schema exists, and the description compensates by listing the returned sections, including the non-zero-days filtering detail. The one unresolved item is the length of the "default window," which an agent may want to reason about; otherwise it is sufficient to invoke 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?

Zero parameters, so a 4 baseline applies. The description does add the one semantic an agent needs — that the time range is a default window rather than caller-specified — which the empty schema cannot convey.

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 and resource ("Read the caller's verification usage overview") and enumerates the returned sections: verdict breakdown, per-check usage, totals, activity series. It is clearly separable from check_balance and list_transactions, which cover different data.

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

Usage Guidelines5/5

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

Explicitly says what the tool is for ("see how many verifications ran and with which verdicts") and routes two adjacent needs to named siblings: token balance to check_balance, individual token movements to list_transactions. Nothing is left to inference about alternatives.

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