Skip to main content
Glama
shahlaukik

Money Manager MCP Server

by shahlaukik

card_list

Retrieve all credit cards in a hierarchical structure to monitor and manage your financial accounts within the Money Manager MCP Server.

Instructions

Retrieves all credit cards in a hierarchical structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'card_list' tool. It validates input, fetches credit card data from '/getCardData' endpoint, calculates total unpaid balance using the toNumber helper, and returns structured card groups with total.
     * Handler for card_list tool
     * Retrieves all credit cards in a hierarchical structure
     */
    export async function handleCardList(
      httpClient: HttpClient,
      input: unknown,
    ): Promise<CardListResponse> {
      CardListInputSchema.parse(input);
    
      const rawResponse = await httpClient.get<CardGroup[]>("/getCardData");
    
      // Calculate total unpaid balance from all card groups
      let totalUnpaid = 0;
      const cardGroups: CardGroup[] = Array.isArray(rawResponse) ? rawResponse : [];
    
      for (const group of cardGroups) {
        if (group.children) {
          for (const card of group.children) {
            // API returns notPayMoney as string, need to parse it
            totalUnpaid += Math.abs(toNumber(card.notPayMoney));
          }
        }
      }
    
      return {
        cardGroups,
        totalUnpaid,
      };
    }
  • Zod input schema for 'card_list' tool, which takes no parameters. Also defines the TypeScript type.
     * Input schema for card_list tool (no parameters)
     */
    export const CardListInputSchema = z.object({});
    
    export type CardListInput = z.infer<typeof CardListInputSchema>;
  • src/index.ts:289-295 (registration)
    MCP tool registration in TOOL_DEFINITIONS array, defining name, description, and input schema for the server to expose the tool.
      name: "card_list",
      description: "Retrieves all credit cards in a hierarchical structure.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
    },
  • Internal registration of the handleCardList function in the toolHandlers object, mapping 'card_list' to its handler.
    // Credit Cards
    card_list: handleCardList,
  • TypeScript interface defining the output response structure for the 'card_list' tool.
    export interface CardListResponse {
      cardGroups: CardGroup[];
      totalUnpaid: number;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states retrieval without details on permissions, rate limits, or what 'hierarchical structure' entails. It lacks behavioral traits like whether it's safe, paginated, or has side effects, leaving significant gaps for an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the purpose without unnecessary words. It could be slightly more structured by including usage hints, but it's appropriately sized for its content.

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

Completeness2/5

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

Given no annotations, no output schema, and a simple tool with 0 parameters, the description is minimal. It states what it does but lacks completeness in behavioral context, return format, or integration with siblings, making it inadequate for full agent understanding.

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?

The tool has 0 parameters with 100% schema description coverage, so no parameter info is needed. The description doesn't add parameter semantics, but this is acceptable as there are no parameters to document, aligning with the baseline for zero parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Retrieves') and resource ('all credit cards'), specifying a hierarchical structure. However, it doesn't differentiate from sibling 'asset_list' or 'transaction_list' tools, which also retrieve lists but for different resources, so it misses explicit sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives, such as 'asset_list' or 'transaction_list', nor does it mention any prerequisites or context for usage. It's a basic statement of function without operational context.

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/shahlaukik/money-manager-mcp'

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