Skip to main content
Glama
ferdhika31

Money Lover MCP Server

Get Wallets

get_wallets

Retrieve all wallets accessible to the authenticated user by providing a JWT token. This tool lists wallets for personal finance management and expense tracking.

Instructions

List all wallets accessible to the authenticated user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenNoJWT token returned by the login tool or derived from EMAIL/PASSWORD environment variables

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletsYes

Implementation Reference

  • src/server.js:340-358 (registration)
    Registration of the get_wallets tool with its name, input/output schema, and handler
    server.registerTool(
      'get_wallets',
      {
        title: 'Get Wallets',
        description: 'List all wallets accessible to the authenticated user.',
        inputSchema: tokenArgument,
        outputSchema: {
          wallets: z.array(z.record(z.any()))
        }
      },
      async ({ token }) => {
        try {
          const wallets = (await runWithClient(token, client => client.getWallets())) ?? [];
          return formatSuccess({ wallets });
        } catch (error) {
          return formatError(error instanceof Error ? error : new Error(String(error)));
        }
      }
    );
Behavior2/5

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

No annotations are provided, and the description only states 'List all wallets...', which implies a read operation but does not explicitly confirm safety, side effects, or authentication requirements beyond the schema parameter.

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?

Single, direct sentence with no unnecessary words. Perfectly concise.

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

Completeness3/5

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

With an output schema present and full schema parameter coverage, the minimal description is adequate for a simple list tool, but lacks mention of possible errors or pagination behavior.

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 coverage is 100%, and the schema's parameter description already covers the token. The tool description adds no additional meaning about the parameter, meeting the baseline for high coverage.

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 uses a specific verb ('List') and resource ('wallets'), and clearly limits scope to 'accessible to the authenticated user', effectively distinguishing it from sibling tools like add_transaction or get_user_info.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, nor any mention of prerequisites or limitations. The agent receives no context for decision-making.

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/ferdhika31/moneylover-mcp'

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