Skip to main content
Glama
theagoralabs

Theagora MCP Server

by theagoralabs

wallet

Read-only

Check wallet balance, spending limits, and transaction details to manage funds within the Theagora marketplace for AI agents.

Instructions

View your wallet balance, spending caps, and daily spend. Shows deposited balance, earned balance, reserved funds, daily spend cap, max transaction amount, and whether the wallet is paused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The wallet tool handler registered with McpServer. Retrieves the agent's ID, calls getWallet API, and returns wallet balance, spending caps, and daily spend as JSON.
    // wallet — Check wallet balance and spending limits
    server.tool(
      'wallet',
      'View your wallet balance, spending caps, and daily spend. Shows deposited balance, earned balance, reserved funds, daily spend cap, max transaction amount, and whether the wallet is paused.',
      {},
      { readOnlyHint: true, openWorldHint: true },
      async () => {
        const agentId = await client.getAgentId();
        const result = await client.getWallet(agentId);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • Registration of the wallet tool using server.tool() with name 'wallet', description, empty params schema (read-only), and handler function.
    // wallet — Check wallet balance and spending limits
    server.tool(
      'wallet',
      'View your wallet balance, spending caps, and daily spend. Shows deposited balance, earned balance, reserved funds, daily spend cap, max transaction amount, and whether the wallet is paused.',
      {},
      { readOnlyHint: true, openWorldHint: true },
      async () => {
        const agentId = await client.getAgentId();
        const result = await client.getWallet(agentId);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • The AgoraApiClient.getWallet helper method that makes an HTTP GET request to /policy-wallets/agent/{agentId} endpoint.
    async getWallet(agentId: string): Promise<any> {
      return this.request(`/policy-wallets/agent/${agentId}`);
    }
Behavior4/5

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

Annotations provide readOnlyHint=true and openWorldHint=true, indicating safe, non-destructive access with potential for varied data. The description adds value by specifying the exact data fields returned (e.g., deposited balance, reserved funds, pause status), which goes beyond annotations to clarify what 'wallet' information is included. It doesn't mention rate limits or auth needs, but annotations cover key behavioral traits adequately.

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 front-loaded and efficient: it starts with the core action ('view your wallet balance, spending caps, and daily spend') and then elaborates with specific details in a single, well-structured sentence. Every part adds value without redundancy, making it highly concise and easy to parse.

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

Completeness4/5

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

Given the tool's low complexity (0 parameters, read-only, no output schema), the description is complete enough for an agent to understand its purpose and output. It lists all key data points, and annotations cover safety and variability. A minor gap is the lack of explicit return format or error handling, but this is acceptable for such a simple tool.

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

Parameters4/5

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

With 0 parameters and 100% schema description coverage, the baseline is 4 as there are no parameters to document. The description appropriately doesn't discuss parameters, focusing instead on the output semantics, which is sufficient given the empty input schema.

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 with specific verbs ('view', 'shows') and enumerates the exact resources it accesses: wallet balance, spending caps, daily spend, deposited balance, earned balance, reserved funds, daily spend cap, max transaction amount, and wallet pause status. It distinguishes itself from siblings like 'deposit', 'place_order', or 'my_purchases' by focusing on wallet metadata rather than transactional actions.

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

Usage Guidelines3/5

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

The description implies usage context by listing what information is shown, suggesting it's for checking wallet status. However, it doesn't explicitly state when to use this tool versus alternatives (e.g., no comparison to 'my_profile' for financial overview or 'check_escrow' for specific funds). The guidance is present but not detailed enough for explicit sibling differentiation.

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

Install Server

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/theagoralabs/mcp'

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