Skip to main content
Glama
shahlaukik

Money Manager MCP Server

by shahlaukik

asset_list

Retrieve all assets in a hierarchical structure to track personal finances through the Money Manager MCP Server.

Instructions

Retrieves all assets in a hierarchical structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the asset_list tool. Fetches asset data from the Money Manager API endpoint /getAssetData, parses input with AssetListInputSchema, calculates total balance using the toNumber helper by summing assetMoney across all assets in groups, and returns AssetListResponse with assetGroups and totalBalance.
    export async function handleAssetList(
      httpClient: HttpClient,
      input: unknown,
    ): Promise<AssetListResponse> {
      AssetListInputSchema.parse(input);
    
      const rawResponse = await httpClient.get<AssetGroup[]>("/getAssetData");
    
      // Calculate total balance from all asset groups
      let totalBalance = 0;
      const assetGroups: AssetGroup[] = Array.isArray(rawResponse)
        ? rawResponse
        : [];
    
      for (const group of assetGroups) {
        if (group.children) {
          for (const asset of group.children) {
            // API returns assetMoney as string, need to parse it
            totalBalance += toNumber(asset.assetMoney);
          }
        }
      }
    
      return {
        assetGroups,
        totalBalance,
      };
    }
  • Zod input schema for the asset_list tool, which requires no parameters (empty object). Used for validation in the handler.
    export const AssetListInputSchema = z.object({});
    
    export type AssetListInput = z.infer<typeof AssetListInputSchema>;
  • src/index.ts:217-223 (registration)
    MCP tool registration in the TOOL_DEFINITIONS array, defining the asset_list tool with its name, description, and empty input schema for the Model Context Protocol server.
      name: "asset_list",
      description: "Retrieves all assets in a hierarchical structure.",
      inputSchema: {
        type: "object" as const,
        properties: {},
      },
    },
  • Internal registration mapping the 'asset_list' tool name to the handleAssetList handler function in the toolHandlers object, used by executeToolHandler.
    asset_list: handleAssetList,
  • TypeScript interface defining the output structure of the asset_list tool response, including hierarchical assetGroups and computed totalBalance.
    export interface AssetListResponse {
      assetGroups: AssetGroup[];
      totalBalance: number;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the output is 'in a hierarchical structure,' which adds some context about the return format, but fails to address critical aspects like whether this is a read-only operation, potential performance impacts for large datasets, authentication requirements, or error conditions.

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 a single, efficient sentence that directly states the tool's function without any fluff or redundancy. It's appropriately sized and front-loaded with the core action, making it easy to parse quickly.

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 the lack of annotations and output schema, the description is incomplete for a tool that retrieves data. It doesn't explain what an 'asset' is in this context, the format of the hierarchical structure, or any limitations (e.g., pagination, sorting). For a data retrieval tool with no structured support, this leaves significant gaps for an AI agent.

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, and the schema description coverage is 100%, so there's no need for parameter documentation in the description. The baseline for 0 parameters is 4, as the description appropriately doesn't waste space on non-existent 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 verb ('Retrieves') and resource ('all assets'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'card_list' or 'transaction_list' that also retrieve lists of different resource types, so it falls short of a perfect score.

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. It doesn't mention why you'd choose 'asset_list' over other list tools like 'card_list' or 'transaction_list', nor does it specify any prerequisites or contextual triggers for its use.

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