Skip to main content
Glama
shahlaukik

Money Manager MCP Server

by shahlaukik

transfer_update

Modify existing transfers in Money Manager by updating date, amount, accounts, or description. Creates a new transaction ID while preserving financial data accuracy.

Instructions

Modifies an existing transfer. WARNING: The server creates a new transfer with a NEW ID instead of updating in-place. The old ID will no longer exist after update. Use transaction_list to get the new ID if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTransfer transaction ID
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

  • Handler function that executes the transfer_update tool logic by validating input and calling the Money Manager /modifyMoveAsset API endpoint. Note the warning about the server creating a new transfer ID.
    export async function handleTransferUpdate(
      httpClient: HttpClient,
      input: unknown,
    ): Promise<TransferOperationResponse> {
      const validated = TransferUpdateInputSchema.parse(input);
    
      const response = await httpClient.post<ApiOperationResponse>(
        "/modifyMoveAsset",
        {
          id: validated.id,
          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: validated.id,
        message:
          response.message ||
          "WARNING: The server creates a new transfer with a NEW ID. The provided ID is now invalid. Use transaction_list to get the new ID.",
      };
    }
  • Zod schema defining the input parameters for the transfer_update tool, including required fields like id, dates, asset IDs, names, and amount.
    export const TransferUpdateInputSchema = z.object({
      id: TransactionIdSchema,
      moveDate: DateSchema,
      fromAssetId: AssetIdSchema,
      fromAssetName: NonEmptyString,
      toAssetId: AssetIdSchema,
      toAssetName: NonEmptyString,
      moveMoney: PositiveNumber,
      moneyContent: z.string().optional(),
      mbDetailContent: z.string().optional(),
    });
    
    export type TransferUpdateInput = z.infer<typeof TransferUpdateInputSchema>;
  • Registration of the transfer_update handler in the toolHandlers object, mapping the tool name to its execution function.
    transfer_update: handleTransferUpdate,
  • src/index.ts:379-409 (registration)
    MCP protocol tool definition registration in TOOL_DEFINITIONS array, including name, description, and JSON schema for input validation.
    {
      name: "transfer_update",
      description:
        "Modifies an existing transfer. WARNING: The server creates a new transfer with a NEW ID instead of updating in-place. The old ID will no longer exist after update. Use transaction_list to get the new ID if needed.",
      inputSchema: {
        type: "object" as const,
        properties: {
          id: { type: "string", description: "Transfer transaction ID" },
          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: [
          "id",
          "moveDate",
          "fromAssetId",
          "fromAssetName",
          "toAssetId",
          "toAssetName",
          "moveMoney",
        ],
      },
    },
  • TypeScript type definition for TransferUpdateInput, extending TransferCreateInput with an id field.
    export interface TransferUpdateInput extends TransferCreateInput {
      id: string;
    }
Behavior5/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 excellently describes critical behavioral traits: the server creates a new transfer with a new ID (not in-place update), the old ID will no longer exist after update, and the need to use transaction_list to retrieve the new ID. This covers mutation behavior, side effects, and workflow implications beyond basic functionality.

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 perfectly structured and concise with just three sentences. The first states the purpose, the second provides critical behavioral warnings, and the third gives practical usage guidance. Every sentence earns its place with essential information, and the warning is appropriately front-loaded.

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

Completeness4/5

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

For a mutation tool with no annotations and no output schema, the description does an excellent job covering behavioral aspects, side effects, and workflow implications. However, it doesn't mention what happens to the old transfer record (whether it's archived, deleted, or marked inactive) or describe the response format, leaving some gaps in completeness.

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%, so the schema already documents all 9 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. However, it does provide important context about how the 'id' parameter relates to the tool's behavior (old ID vs new ID), which adds some semantic value.

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 clearly states the specific action ('Modifies an existing transfer') and resource ('transfer'), distinguishing it from sibling tools like transfer_create (creates new) and transaction_update (updates transactions, not transfers). The verb 'modifies' is precise and differentiates from creation or deletion operations.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool vs alternatives: it warns that this creates a new transfer with a new ID instead of updating in-place, and explicitly mentions using transaction_list to get the new ID if needed. This gives clear context about the tool's behavior and prerequisites.

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