Skip to main content
Glama

Get API usage statistics

autoshort_get_usage_stats
Read-onlyIdempotent

Retrieve API credit balance, today and total call counts, and recent credit transactions to monitor usage; requires the usage:read scope.

Instructions

API usage statistics: credit balance, API call counts (today/total) and recent credit transactions. Requires the "usage:read" scope. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond them: the required "usage:read" scope and that the call costs no credits. It says nothing about rate limits, freshness of the counters, or how many transactions are returned, though with no output schema the field enumeration does double duty.

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?

A single sentence, front-loaded with the resource and its payload, followed by the two operational facts that matter (scope, cost). No filler and no repetition of the title.

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-only tool this covers the essentials: what is returned, what scope is needed, and that it is free. The remaining gap is that there is no output schema, so details like transaction count or counter reset time are left unspecified, but that is minor here.

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 the baseline is 4; there is nothing for the description to disambiguate. Schema coverage is 100% and consistent with an empty argument object.

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 resource (API usage statistics) and enumerates exactly what comes back: credit balance, call counts today/total, and recent credit transactions. It is slightly muddied by including 'credit balance', which overlaps with the sibling autoshort_get_credit_balance, without saying how the two differ.

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 description gives a prerequisite (the "usage:read" scope) and notes the call is free, which implies usage context. It never says when to prefer this over autoshort_get_credit_balance or autoshort_get_limits, so the agent must infer the choice from the payload listing.

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