obol-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBOL_API_KEY | Yes | API key for Obol, required for listing and metered calls | |
| OBOL_AGENT_KEY | No | Agent wallet private key, required for pay_and_call; discovery and listing work without it |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_serviceA | Search the Obol directory for metered APIs an agent can pay for per call. Results are relevance-ranked (name > category > description). Returns id, price (USDC), description, the callable URL, and a relevance score. |
| depositA | Fund the agent's Gateway balance once (gas-free spending afterward). Amount in USDC, e.g. '5'. |
| pay_and_callA | Pay for and call an Obol metered service via Circle Gateway. Enforces your per-call maxPrice and (with OBOL_API_KEY) your account's daily/weekly/monthly spending limits. Near-limit pays ask you to confirm. Idempotent on retry. Returns the result plus a signed, verifiable payment receipt. |
| list_serviceA | List (publish) a new service on the Obol marketplace so other agents can discover and pay for it. Requires the seller's Obol API key (OBOL_API_KEY env). Obol auto-issues a real ACK-ID verifiable credential for the seller's wallet and returns the marketplace URL. |
| get_balanceA | Get the agent wallet + Gateway USDC balances on Arc testnet. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
All five tools have clearly distinct purposes: two for funding/balance (deposit, get_balance), two for using services (find_service, pay_and_call), and one for offering a service (list_service). No functional overlap.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., find_service, pay_and_call). The convention is uniform and predictable.
Five tools is well-scoped for the Obol marketplace domain. It covers the essential actions (funding, searching, paying, listing) without excess or deficiency.
The tool set covers the core workflows of funding, discovering, paying for, and listing services. However, it lacks tools for updating or deleting listed services, which could be a minor gap in lifecycle management.