Skip to main content
Glama

AANet

by space.aanet
OverviewDiscussionsAdmin

aanet_deposit

Fund a real workspace via the x402 protocol — a two-step call using the same tool both times. This does not accept trial workspaces (use aanet_create_workspace for a fundable one) and requires the owner_key.

Step 1 — call with only api_key/workspace_id/amount_usd: returns an x402
PaymentRequired challenge offering USDC on Base, Polygon, Arbitrum,
Avalanche, and Solana as payment options; nothing is charged yet.
Step 2 — sign that challenge
with your own wallet/x402 client (this tool cannot sign for you) and
call again with the identical amount_usd plus the resulting proof as
payment_signature; on success this verifies and settles against the
facilitator and returns {workspace_id, deposited_units, tx_hash,
network}. A failed or already-used signature raises an error rather than
silently no-op'ing.

Input Schema

TableJSON 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.
amount_usdYesDeposit amount in US dollars as a decimal string, e.g. "1.00". Minimum $0.25.
workspace_idYesThe workspace_id from aanet_create_workspace or aanet_create_trial_workspace.
payment_signatureNoLeave unset on your first call to receive the payment challenge. Set this to the signed proof from your own x402-aware wallet client on the follow-up call with the same amount_usd, to actually settle the payment and credit the balance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / amount_usd / description
      Added value: +"Deposit amount in US dollars as a decimal string, e.g. \"1.00\". Minimum $0.25."
    • 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 / payment_signature / description
      Added value: +"Leave unset on your first call to receive the payment challenge. Set this to the signed proof from your own x402-aware wallet client on the follow-up call with the same amount_usd, to actually settle the payment and credit the balance."
    • addedInput schema / properties / workspace_id / description
      Added value: +"The workspace_id from aanet_create_workspace or aanet_create_trial_workspace."
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It discloses that the first call charges nothing, the second call settles, the tool cannot sign challenges itself, failed or reused signatures error instead of no-op'ing, and success returns specific fields. This is exemplary transparency for a mutation-like payment tool.

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?

The description is longer than average but every sentence earns its place, given the two-step protocol. It front-loads the core purpose and key restrictions, then uses numbered steps with clear conditions imparted in sequence. No filler or redundant restatement of the tool name appears.

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?

This tool has no output schemacarska and moderate complexity, but the description fully compensates by enumerating the success return fields, the networks offered, the minimum amount, error behavior, and step-specific parameter usage. An agent has all the information needed to correctly execute both calls.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds substantial meaning beyond parameter names and types: it ties amount_usd to an identical-value requirement across both calls, explains payment_signature as the signed proof and when to leave it unset, and clarifies the api_key must be the owner_key. This goes well beyond the schema's field descriptions.

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 clearly states the tool's purpose: funding a real workspace via the x402 protocol in two steps. It distinguishes itself from trial workspace creation and names the sibling tool for creating a fundable workspace, leaving no ambiguity about its scope.

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?

It explicitly says when to use this tool versus alternatives, noting that trial workspaces are not accepted and pointing to aanet_create_workspace for a fundable one. It also provides structured step-by-step usage instructions, including when to omit payment_signature and when to provide it, and highlights the owner_key requirement.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources