Skip to main content
Glama

ai_usage

Read-onlyIdempotent

Return this month's AI spend broken down by feature (transcribe, tts, generate_image, complete). Read-only; no charges.

Example:

{}
// Returns: { "complete": { "calls": 142, "cost": "$0.23" }, "tts": { "calls": 12, "cost": "$0.003" }, ... }

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": "ai_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description still adds 'no charges,' which clarifies that invoking the tool does not incur AI spend — a non-obvious behavioral fact. The inline example return payload also discloses the response shape, which annotations do not.

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?

One sentence of purpose, one clause of behavioral caveat, then an example — all front-loaded with zero filler. The example earns its space because there is no output schema to convey the return shape.

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 zero-parameter read tool with no output schema, the definition supplies scope, the breakdown keys, the cost unit, and a concrete response sample, which is nearly everything an agent needs. The only gap is not stating what happens before any spend exists or whether features with zero usage appear.

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 baseline of 4 applies. The description correctly reinforces that no arguments are needed via the empty-object example.

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?

Names a specific verb and resource (return) and resource (this month's AI spend), and enumerates the breakdown dimensions (transcribe, tts, generate_image, complete), so an agent knows exactly what it gets back. It stops short of naming a sibling such as usage_summary to disambiguate the coarser aggregate from this per-feature breakdown.

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 scope 'this month's' implicitly tells the agent there is no date-range argument and that only the current period is available, which is useful usage context. However, there is no explicit when-to-use versus when-not or a named alternative, so the agent must infer that usage_summary is the tool for other periods or account-wide totals.

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