Skip to main content
Glama

aqb_cash_out

Redeems AQB 1:1 for USDC from an on-chain vault on Base so agents can cash out by providing an AQB amount and optional account.

Instructions

Alias for aqb_redeem

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": {
      "aqb": "<aqb>"
    },
    "name": "aqb_cash_out"
  }
}

Input Schema

NameRequiredDescriptionDefault
aqbYes
accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/5.0
Behavior1/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 of behavioral disclosure. It reveals no side effects, permissions, mutation behavior, or other operational traits beyond the bare alias statement.

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

Conciseness2/5

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

The description is extremely short and front-loaded, but it is under-specified rather than appropriately concise. The single fragment does not provide enough structure to guide an agent's invocation.

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

Completeness1/5

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

The tool has no annotations, no output schema, and two undocumented parameters. The description does not compensate for any of these gaps, so it is not complete enough to support correct invocation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the required aqb parameter or the optional account parameter. It adds no meaning beyond the bare parameter names in the schema.

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 only states that the tool is an alias for aqb_redeem; it does not independently state the verb, resource, or operation. The alias relationship gives some purpose signal, but an agent must already know what aqb_redeem does to understand this tool.

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 guidance on when to use this alias rather than aqb_redeem or any other sibling. The description does not explain whether the two tools are interchangeable or whether this one has different constraints.

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