ae_get_wallet
Get the wallet balance and details for an agent.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | UUID of the agent |
remno
by sh.remno.api
TDQS
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavioral traits. It only states the operation without mentioning side effects, return format, error conditions, or prerequisites.
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?
Single sentence, no waste, and front-loaded with the key action and resource.
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?
Tool is simple, but 'details' is vague and no output schema exists. The description doesn't clarify what 'details' includes or how balance is represented, leaving some ambiguity.
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?
The schema already provides 100% coverage for agent_id ('UUID of the agent'). The description's 'for an agent' adds little new meaning, so baseline 3 applies.
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 uses the specific verb 'Get' and names the resource 'wallet balance and details for an agent,' making it clear and distinct from sibling getter tools like ae_get_service or ae_get_transaction.
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 is provided. It doesn't mention when to use this over alternatives, nor any context or exclusions.
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.
TDQS
A4/5.0
Disambiguation5/5
Each tool targets a distinct resource and action, from service discovery and registration to transaction negotiation and output verification. The only overlapping pair, ae_discover_services and ae_list_services, is explicitly differentiated by semantic search vs. categorical browsing.
Naming Consistency5/5
All tools follow the consistent ae_verb_noun pattern in snake_case, with verbs like create, get, list, deliver, and verify. The uniform prefix and naming convention make the API predictable and easy to navigate.
Tool Count5/5
With 13 tools, the server is well-scoped for a marketplace platform, covering service lifecycle, transaction workflow, wallet, trust, and agent management. Each tool serves a distinct purpose and none feel redundant, keeping the surface area manageable.
Completeness4/5
The tool set covers the full service and transaction lifecycle: register/list/discover/get services, create/negotiate/deliver/verify transactions, plus wallet and trust queries. Minor gaps exist such as no service update/delete or transaction listing, but core workflows are fully supported.