AgentWallet MCP Server

get_usage

Retrieves current month usage statistics for AgentWallet, returning operation counts and remaining capacity under the free fair-use ceiling so agents can track consumption limits.

Instructions

Get the current month's usage statistics. Hosted AgentWallet is free: returns the operations count and what is left under the fair-use ceiling.

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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.14.2Oct 14, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedv1.7.3Mar 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses the return contents and the free/fair-use context, but it does not mention read-only behavior, authentication requirements, rate limits, or any other operational constraints.

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?

The description is two concise sentences with the core purpose front-loaded and no redundant wording. The second sentence adds useful return-value and fair-use context without bloating the definition.

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 simple zero-parameter read tool with no output schema, the description gives an adequate summary of what comes back: operations count and remaining fair-use allowance. It could be more complete by specifying units or response shape, but nothing critical is missing for selecting and invoking the tool.

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 has zero parameters and the schema is empty, so there are no parameter meanings for the description to clarify. The baseline for a zero-parameter tool is 4, and no additional parameter information is needed here.

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?

The description uses a specific verb and resource: it gets the current month's usage statistics, then clarifies that it returns the operations count and remaining fair-use allowance. This clearly identifies the tool's job, though it does not explicitly distinguish it from similar-looking siblings such as get_allowance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool returns but gives no explicit guidance on when to use it, when not to use it, or which sibling tools are alternatives. The usage context is only implicit from the phrase "current month's usage statistics."

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