Skip to main content
Glama

AANet

by space.aanet
OverviewDiscussionsAdmin

aanet_request_refund

Ask for a workspace's entire remaining balance back, when its task is done and money is left over — call this before aanet_delete_workspace, not after. Owner_key required; trial workspaces reject this outright (they never held real money).

This reserves (zeros out) the full balance immediately, so a second call
with nothing left to refund fails rather than double-paying out. The
real network fee for the payout is deducted from what you receive
(net_payout_usd in the response = gross - fee); if the balance doesn't
even cover the estimated fee, this call fails instead of reserving
anything. Payout is processed manually by the operator, not instantly —
poll aanet_get_refund_status for the outcome rather than assuming
success once this call returns.

Input Schema

NameRequiredDescriptionDefault
api_keyYesBearer credential for this workspace: either the owner_key returned once by aanet_create_workspace/aanet_create_trial_workspace, or a sub-key returned by aanet_mint_subkey. Sent under the hood as `Authorization: Bearer <api_key>`. Owner-only tools reject a sub-key with a 403.
networkYesPayout network: one of "base", "polygon", "arbitrum", "avalanche", "solana".
workspace_idYesThe workspace_id from aanet_create_workspace or aanet_create_trial_workspace.
destination_addressYesYour own wallet address on that network to receive the payout.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / network / description
      Previous value: -"Payout network: \"base\" or \"solana\"."New value: +"Payout network: one of \"base\", \"polygon\", \"arbitrum\", \"avalanche\", \"solana\"."
  2. Changed4 schema fields changed
    • addedInput schema / properties / api_key / description
      Added value: +"Bearer credential for this workspace: either the owner_key returned once by aanet_create_workspace/aanet_create_trial_workspace, or a sub-key returned by aanet_mint_subkey. Sent under the hood as `Authorization: Bearer <api_key>`. Owner-only tools reject a sub-key with a 403."
    • addedInput schema / properties / destination_address / description
      Added value: +"Your own wallet address on that network to receive the payout."
    • addedInput schema / properties / network / description
      Added value: +"Payout network: \"base\" or \"solana\"."
    • addedInput schema / properties / workspace_id / description
      Added value: +"The workspace_id from aanet_create_workspace or aanet_create_trial_workspace."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: it discloses that the balance is reserved/zeroed immediately, that a second call fails rather than double-paying, that the network fee is deducted (net_payout_usd = gross - fee), that insufficient balance relative to the fee causes failure before reserving, and that payout is manual rather than instant.

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?

Front-loads the purpose and the ordering constraint, then layers in behavioral details. The prose is dense but every sentence contributes a distinct behavioral fact; it is slightly long but not padded.

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

Completeness5/5

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

For a mutation tool with no annotations and no output schema, the description covers preconditions, side effects, failure modes, fee handling, one response field, and the polling follow-up. Nothing an agent needs to invoke it correctly is missing.

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%, so all four parameters are already documented in the schema, establishing the baseline of 3. The description only restates the owner_key requirement, adding little beyond what the schema's api_key description already says.

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?

States a specific verb and resource ('Ask for a workspace's entire remaining balance back') with clear scope ('entire remaining balance'). It explicitly positions itself relative to sibling aanet_delete_workspace ('call this before ... not after'), so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit preconditions (task done, money left over), ordering relative to a named sibling, and exclusions (trial workspaces reject this outright, owner_key required). It also names the follow-up tool, aanet_get_refund_status, for the outcome.

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

All AANet toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources