Skip to main content
Glama

Aquedra Run

View account usage

get_usage
Read-onlyIdempotent

Read the account's credit balance (balance_usd, in US dollars as decimal text), its level (trial or paid) and limits, whether the one-time trial credits were granted, whether credit purchases are open, and the most recent credit movements.

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the actual return content, including the units and text encoding of balance_usd and the trial-credit state. It stops short of saying how many "most recent credit movements" are returned or over what window, which is a real gap.

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?

One front-loaded sentence with no filler, and the balance is mentioned first, which is the most likely reason to call it. It is a dense enumerated list, slightly run-on, but every clause names a distinct returned field.

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 no output schema, the description carries the full burden of explaining return values and does so thoroughly across balance, level, limits, trial status, purchase availability, and recent movements. Only the cardinality/window of credit movements and any auth or rate-limit context are missing.

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?

There are zero parameters, so the baseline is 4. The description still earns credit by clarifying that balance_usd is US dollars expressed as decimal text, removing ambiguity an agent would otherwise guess at.

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?

The description opens with a specific verb and resource ("Read the account's credit balance") and then enumerates the exact fields returned, rescuing a fairly generic name like get_usage. An agent can immediately tell this is the read-side counterpart to buy_credits without opening a schema.

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 only implied: checking balance and purchase availability before calling buy_credits is the obvious use, but the description never states when to call it, when not to, or names any alternative. No prerequisites or exclusions are given.

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