Skip to main content
Glama
shahlaukik

Money Manager MCP Server

by shahlaukik

transfer_create

Create transfers between assets to manage money movement in your financial accounts. Specify source, destination, amount, and date to record asset transfers.

Instructions

Transfers money between two assets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moveDateYesTransfer date (YYYY-MM-DD)
fromAssetIdYesSource asset ID
fromAssetNameYesSource asset name
toAssetIdYesDestination asset ID
toAssetNameYesDestination asset name
moveMoneyYesTransfer amount
moneyContentNoOptional: Description
mbDetailContentNoOptional: Detailed notes

Implementation Reference

  • The core handler function that implements the transfer_create tool. Validates input using TransferCreateInputSchema, calls the Money Manager API /moveAsset endpoint with POST request, and returns a TransferOperationResponse.
    export async function handleTransferCreate(
      httpClient: HttpClient,
      input: unknown,
    ): Promise<TransferOperationResponse> {
      const validated = TransferCreateInputSchema.parse(input);
    
      const response = await httpClient.post<ApiOperationResponse>("/moveAsset", {
        moveDate: validated.moveDate,
        fromAssetId: validated.fromAssetId,
        fromAssetName: validated.fromAssetName,
        toAssetId: validated.toAssetId,
        toAssetName: validated.toAssetName,
        moveMoney: validated.moveMoney,
        moneyContent: validated.moneyContent || "",
        mbDetailContent: validated.mbDetailContent || "",
      });
    
      return {
        success: response.success !== false && response.result !== "fail",
        transferId: response.transferId || response.id,
        message: response.message,
      };
    }
  • Zod schema for input validation of the transfer_create tool parameters, including required fields like moveDate, asset IDs/names, and amount.
    export const TransferCreateInputSchema = z.object({
      moveDate: DateSchema,
      fromAssetId: AssetIdSchema,
      fromAssetName: NonEmptyString,
      toAssetId: AssetIdSchema,
      toAssetName: NonEmptyString,
      moveMoney: PositiveNumber,
      moneyContent: z.string().optional(),
      mbDetailContent: z.string().optional(),
    });
    
    export type TransferCreateInput = z.infer<typeof TransferCreateInputSchema>;
  • src/index.ts:352-378 (registration)
    MCP tool registration definition for transfer_create, including name, description, and JSON Schema for input validation exposed to MCP clients.
      name: "transfer_create",
      description: "Transfers money between two assets.",
      inputSchema: {
        type: "object" as const,
        properties: {
          moveDate: { type: "string", description: "Transfer date (YYYY-MM-DD)" },
          fromAssetId: { type: "string", description: "Source asset ID" },
          fromAssetName: { type: "string", description: "Source asset name" },
          toAssetId: { type: "string", description: "Destination asset ID" },
          toAssetName: { type: "string", description: "Destination asset name" },
          moveMoney: { type: "number", description: "Transfer amount" },
          moneyContent: { type: "string", description: "Optional: Description" },
          mbDetailContent: {
            type: "string",
            description: "Optional: Detailed notes",
          },
        },
        required: [
          "moveDate",
          "fromAssetId",
          "fromAssetName",
          "toAssetId",
          "toAssetName",
          "moveMoney",
        ],
      },
    },
  • Internal registry mapping the 'transfer_create' tool name to its handler function within the toolHandlers object.
    transfer_create: handleTransferCreate,
  • Registration of the TransferCreateInputSchema in the central ToolSchemas registry used for runtime validation.
    transfer_create: TransferCreateInputSchema,
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Transfers money' implies a write/mutation operation, the description doesn't address critical behavioral aspects like authorization requirements, whether the transfer is immediate or scheduled, what happens if assets don't exist, or what confirmation/response to expect.

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 extremely concise at just one sentence with no wasted words. It's front-loaded with the core purpose and doesn't contain any unnecessary information or repetition.

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?

For a financial transfer tool with 8 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address the tool's behavior, error conditions, response format, or relationship to sibling tools, leaving significant gaps in understanding how to use it effectively.

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?

With 100% schema description coverage, all 8 parameters are documented in the schema. The description doesn't add any meaningful parameter semantics beyond what's already in the schema descriptions, so it meets the baseline expectation but doesn't provide additional value.

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 ('Transfers money') and resources ('between two assets'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'transfer_update', which could also involve money transfers between assets.

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. With sibling tools like 'transaction_create' and 'transfer_update' available, there's no indication of when this specific transfer creation tool is appropriate versus other financial operations.

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