Skip to main content
Glama
shahlaukik

Money Manager MCP Server

by shahlaukik

init_get_data

Retrieves initial financial data including categories, payment types, asset groups, and multi-book configuration for Money Manager MCP Server.

Instructions

Retrieves initial application data including categories, payment types, asset groups, and multi-book configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mbidNoOptional: Money book ID

Implementation Reference

  • The main handler function for the init_get_data tool. It validates input, calls the Money Manager API /getInitData endpoint, and transforms the raw response into the expected InitDataResponse format.
    /**
     * Handler for init_get_data tool
     * Retrieves initial application data including categories, payment types, etc.
     */
    export async function handleInitGetData(
      httpClient: HttpClient,
      input: unknown,
    ): Promise<InitDataResponse> {
      const validated = InitGetDataInputSchema.parse(input);
    
      const params: Record<string, string | undefined> = {};
      if (validated.mbid) {
        params["mbid"] = validated.mbid;
      }
    
      const rawResponse = await httpClient.get<RawInitDataResponse>(
        "/getInitData",
        params,
      );
    
      // Transform the raw response to the expected format
      return {
        initData: rawResponse.initData,
        categories: {
          income: rawResponse.category_0 || [],
          expense: rawResponse.category_1 || [],
        },
        paymentTypes: rawResponse.payType || [],
        multiBooks: rawResponse.multiBooks || [],
        assetGroups: rawResponse.assetGroups || [],
        assetNames: rawResponse.assetNames || [],
      };
    }
  • Zod schema defining the input for init_get_data tool: optional mbid string.
    /**
     * Input schema for init_get_data tool
     */
    export const InitGetDataInputSchema = z.object({
      mbid: z.string().optional(),
    });
    
    export type InitGetDataInput = z.infer<typeof InitGetDataInputSchema>;
  • Registration of the handleInitGetData function in the toolHandlers map used for tool execution.
    init_get_data: handleInitGetData,
  • src/index.ts:30-43 (registration)
    MCP protocol tool definition registration, including name, description, and JSON schema for input validation.
    {
      name: "init_get_data",
      description:
        "Retrieves initial application data including categories, payment types, asset groups, and multi-book configuration.",
      inputSchema: {
        type: "object" as const,
        properties: {
          mbid: {
            type: "string",
            description: "Optional: Money book ID",
          },
        },
      },
    },
  • Registration of the input schema in the ToolSchemas registry for validation lookup.
    init_get_data: InitGetDataInputSchema,
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it 'retrieves' data, implying a read-only operation, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error conditions, or what 'initial' means in context (e.g., one-time setup vs. cached data). This leaves gaps for a tool that likely serves critical configuration data.

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 front-loads the core action ('retrieves') and lists the data components clearly. There is no wasted verbiage, and it directly communicates the tool's purpose without redundancy.

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?

Given the tool's moderate complexity (retrieving multiple data types for application setup), no annotations, no output schema, and 100% schema coverage, the description is minimally adequate. It specifies what data is retrieved but lacks details on behavior, output format, or error handling. For a setup tool with no structured output, more context would be helpful, but it meets the baseline for a read operation.

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 description coverage is 100%, with one optional parameter 'mbid' documented as 'Money book ID.' The description adds no parameter-specific semantics beyond implying it retrieves 'multi-book configuration,' which loosely relates to 'mbid.' Since the schema covers the parameter adequately, the baseline score of 3 is appropriate, as the description doesn't significantly enhance parameter understanding.

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 specifies the resources: 'initial application data including categories, payment types, asset groups, and multi-book configuration.' It distinguishes itself from siblings by focusing on initial setup data rather than CRUD operations on specific entities like assets or transactions. However, it doesn't explicitly contrast with sibling tools like 'dashboard_get_overview' or 'summary_get_period' which might also retrieve data.

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 prerequisites (e.g., when initial data is needed), exclusions, or comparisons to sibling tools like 'dashboard_get_overview' or 'summary_get_period' that might retrieve overlapping data. The agent must infer usage from the name and description alone.

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