Skip to main content
Glama
inviti8

Obolus

by inviti8

wallet_funding_info

Get funding directions and QR codes to top up your Algorand vault, and see which of three setup steps still needs action.

Instructions

Explain how to put money in this wallet, and report which of the three setup steps the vault is on.

For the human, not the agent - it returns an address and instructions, and no part of it can be automated by the agent.

The three steps are in a forced order: ALGO must arrive before the vault can opt into the payment asset, and the opt-in must happen before USDC can be received at all. USDC sent to a vault that has not opted in is rejected outright - it does not sit pending, it fails.

Each step a human performs carries a scan value: an ARC-26 URI an Algorand wallet can scan. It encodes the address AND the asset id, so the sender cannot aim at the wrong asset by hand - which matters because sending the wrong one is rejected rather than held. No amount is encoded; the human types that into their own wallet where they see it before confirming.

TOPPING UP ONE ASSET. Pass asset - "ALGO", "USDC", or the asset id - and the reply narrows to that asset's steps AND includes the QR code as an image, so the human can scan it directly. ALGO codes are black; the payment asset's are blue and captioned, so the two are not confused at a glance. Omit asset for the whole picture as text.

The usual flow: wallet_status answers "how much do I have", then wallet_funding_info(asset="USDC") answers "I want to top up USDC".

SET open_in_browser WHENEVER A HUMAN WANTS TO SCAN THE CODE. The image block this returns renders in some MCP clients and not in a terminal, so on its own it can reach the model and never reach the person holding the phone. With the flag, Obolus writes a self-contained page and opens it in the default browser - no server and no network needed.

qr_dir optionally writes the codes as PNG files into that directory, under the same configured file root as body_file/output_file. obolus vault qr prints them straight into a terminal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetNo
qr_dirNo
open_in_browserNo
Install Server

TDQS

A5/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 thoroughly. It discloses that the tool is for a human and cannot be automated, that USDC sent before opt-in is rejected rather than held, that the QR encodes address and asset id but not amount, that image blocks may not render in terminals, and that qr_dir writes files to disk.

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 long but every sentence carries substantive guidance: setup order, failure semantics, QR contents, parameter effects, browser behavior, and file output. It is front-loaded with the core purpose and then organized by parameter and usage scenario, so an agent can quickly extract the decision-relevant parts.

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?

Given three optional parameters, no annotations, and no output schema, the description is complete enough for an agent to select the tool and invoke it correctly. It explains what the tool returns, how to choose parameters, the human-only nature, and how it fits alongside wallet_status.

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?

Schema description coverage is 0%, so the description must explain all parameters itself. It covers `asset` values ('ALGO', 'USDC', asset id, or omitted), `open_in_browser` behavior including rendering limitations and the self-contained page, and `qr_dir` including PNG output and the same file root as body_file/output_file.

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 opens with a specific verb and resource: it explains how to fund the wallet and reports which of the three setup steps the vault is on. It also clarifies that it returns human-facing address and instructions, and it distinguishes itself from wallet_status by naming the usual flow where wallet_status answers balances and wallet_funding_info answers top-up questions.

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?

The description gives explicit usage guidance: pass `asset` to narrow to one asset and omit it for the full picture, set `open_in_browser` when a human wants to scan the code, and provides the sibling relationship by saying wallet_status is for 'how much do I have' while wallet_funding_info is for 'I want to top up USDC'.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/inviti8/Obolus'

If you have feedback or need assistance with the MCP directory API, please join our Discord server