Skip to main content
Glama

Get detailed usage statistics

get_usage
Read-only

Return detailed usage statistics for the account over a period (day, week, or month): total credits used, emails processed, request counts broken down by endpoint and source, a daily breakdown, and recent activity.

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
limitNoMax recent log entries to include (default 100, max 1000).
periodNoReporting period. Default 'month'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / minimum
      Added value: +-9007199254740991
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered and the description needn't restate it. What the description adds is the composition of the result payload — aggregate totals plus a daily breakdown plus recent activity — which is genuinely new information given there is no output schema. It omits auth scoping (account vs workspace) and any cost or latency expectation, which keeps it from 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.

Conciseness4/5

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

A single front-loaded sentence: verb, resource, scope, then the enumerated contents. No filler or marketing language. The dense parenthetical enumeration of metrics is slightly list-like but each item corresponds to real returned data, so nothing is gratuitous.

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?

With only two optional parameters, three read-only annotations, and no output schema, the description carries the main burden of explaining the return payload, and it does enumerate the key fields. The remaining gap is scope — whether statistics are account-wide or per-key — and confirmation of the default period behavior beyond the schema's 'month' note.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented, and the description only echoes the period enum values without adding format or default semantics. The limit parameter for recent log entries is not mentioned at all in the description. Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb and resource ("Return detailed usage statistics for the account") and enumerates the contained metrics: credits used, emails processed, request counts by endpoint and source, daily breakdown, recent activity. An agent knows exactly what data class this yields. It does not explicitly contrast with the nearby get_credits or get_account siblings, so it stops short of a 5.

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?

Usage is implied rather than stated: the period framing (day, week, month) signals 'reporting snapshot' use, but there is no explicit when-to-use, no exclusion, and no pointer to get_credits for a credits-only query. An agent must infer the boundary from names alone, which the rubric treats as minimum-viable guidance.

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.