Skip to main content
Glama

My wallet

agentwares_wallet

Credit balance, totals earned and spent, and the 50 most recent transactions.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour Agentwares API key. Optional when the MCP connection already sends an Authorization: Bearer header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the return shape (balance, totals, 50 most recent transactions) and implies a read operation, but says nothing about authentication behavior beyond the schema, rate limits, whether the 50-item cap is paginated, transaction ordering, or empty-wallet behavior. For a ledger tool with zero annotation coverage, this is thin.

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 compact sentence that front-loads the main payload (credit balance) and then enumerates extras. It is efficient and front-loaded, though it reads as a fragment without a leading verb like 'Returns'.

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?

No output schema exists, so the description does the work of telling the agent what comes back, and it does so at a high level: balance, totals, recent transactions. Gaps remain on pagination beyond 50 transactions and ordering, but for a simple read tool this is largely complete.

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 description coverage is 100%, and the single api_key parameter is fully documented in the schema including the Bearer-header alternative. The description adds nothing about the parameter, which is acceptable given the schema. 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 the specific resource returned: credit balance, totals earned and spent, and the 50 most recent transactions. This is a clear read of wallet contents. It doesn't explicitly differentiate from siblings, though no sibling clearly overlaps, so 4 rather than 5.

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?

No when-to-use guidance, no exclusions, and no alternatives named. The agent must infer that this is the tool for checking balance and recent transactions. It does not say when wallet data is preferred over something like agentwares_sales.

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