Skip to main content
Glama

Loyalty tier and credit balance

agentgas_wallet
Read-only

Free. Delivered orders, current flat fee ($0.10 / $0.05 after 3 / $0.02 after 10), orders to the next tier, and prepaid credit balance for a wallet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "agentgas_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context by disclosing that the call is free and by enumerating the returned wallet metrics, including the fee tiers and prepaid credit balance.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with 'Free', but it reads as a fragmented list rather than a structured explanation. It avoids waste, yet the terse phrasing makes key concepts like 'orders to the next tier' harder to parse than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter wallet lookup with no output schema, the description does enumerate the main return values, which is helpful. It still leaves the agent to infer the exact action, address format, and when this tool should be chosen over sibling wallet or status tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the single required parameter is an address. The description only implies that this address identifies a wallet, but it does not explain address format, requiredness, or what wallet types are accepted, so it only partially compensates for the missing schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists the wallet data returned, including delivered orders, fee schedule, progress to next tier, and credit balance, so the general resource is inferable. However, it lacks a clear verb such as 'get' or 'retrieve' and does not explicitly distinguish this lookup from sibling tools like agentgas_status or agentgas_quote.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor any stated exclusions or prerequisites. 'Free' is the only contextual note, but it does not tell the agent when this wallet-summary tool is the right choice.

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