Skip to main content
Glama

Read remaining allowance and spending limits

get_usage
Read-onlyIdempotent

Read the supplied trial or connection API key allowance and expiry. No completed-check unit is consumed. Does not change any limits or authorize spending.

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
trial_tokenNoOptional short-lived free trial token from get_trial_access. Never place a paid API key here; use the connection Authorization header for paid access.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world. The description adds billing-relevant context annotations cannot express: no completed-check unit is consumed, and it 'does not change any limits or authorize spending' — a meaningful clarification of side-effect scope for something named 'usage'.

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 short sentences, front-loaded with the read action, followed by cost and side-effect qualifiers. No filler or repetition.

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?

A single-optional-parameter read tool with full annotations and full schema coverage needs little more; the description even sketches the return content (allowance and expiry) despite no output schema. Only the absence of explicit sibling routing keeps it from the top.

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% and the schema already documents the trial_token pattern and the 'never place a paid API key here' warning. The description's phrase 'trial or connection API key' lightly reinforces the two-mode access model but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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: 'Read the supplied trial or connection API key allowance and expiry.' An agent can tell this is a key/allowance inspection tool distinct from its siblings, though the description never names an alternative to disambiguate against get_trial_access or check_asset.

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 by 'Read the supplied ... allowance and expiry' and the note that no completed-check unit is consumed, which hints at cheap status checks. However, there is no explicit when-to-use versus get_trial_access/check_asset, and no stated prerequisites or exclusions.

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