Skip to main content
Glama
shahlaukik

Money Manager MCP Server

by shahlaukik

card_update

Modify credit card details like name, linked payment account, and billing dates to keep financial records current and accurate.

Instructions

Modifies an existing credit card.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetIdYesCard asset ID
cardNameYesCredit card name
linkAssetIdYesLinked payment asset ID
linkAssetNameYesLinked payment asset name
jungsanDayNoOptional: Balance calculation day (1-31)
paymentDayNoOptional: Payment due day (1-31)

Implementation Reference

  • The main handler function for the card_update tool. Validates input, calls Money Manager /modifyCard API, returns CardOperationResponse.
    /**
     * Handler for card_update tool
     * Modifies an existing credit card
     */
    export async function handleCardUpdate(
      httpClient: HttpClient,
      input: unknown,
    ): Promise<CardOperationResponse> {
      const validated = CardUpdateInputSchema.parse(input);
    
      const response = await httpClient.post<ApiOperationResponse>("/modifyCard", {
        assetId: validated.assetId,
        cardName: validated.cardName,
        linkAssetId: validated.linkAssetId,
        linkAssetName: validated.linkAssetName,
        jungsanDay: validated.jungsanDay,
        paymentDay: validated.paymentDay,
      });
    
      return {
        success: response.success !== false && response.result !== "fail",
        cardId: validated.assetId,
        message: response.message,
      };
    }
  • Zod schema for validating card_update input parameters: assetId, cardName, linkAssetId, linkAssetName, optional jungsanDay and paymentDay.
     * Input schema for card_update tool
     */
    export const CardUpdateInputSchema = z.object({
      assetId: AssetIdSchema,
      cardName: NonEmptyString,
      linkAssetId: AssetIdSchema,
      linkAssetName: NonEmptyString,
      jungsanDay: DayOfMonthSchema.optional(),
      paymentDay: DayOfMonthSchema.optional(),
    });
    
    export type CardUpdateInput = z.infer<typeof CardUpdateInputSchema>;
  • src/index.ts:324-348 (registration)
    MCP tool registration in TOOL_DEFINITIONS array, defining name, description, and inputSchema for card_update.
    {
      name: "card_update",
      description: "Modifies an existing credit card.",
      inputSchema: {
        type: "object" as const,
        properties: {
          assetId: { type: "string", description: "Card asset ID" },
          cardName: { type: "string", description: "Credit card name" },
          linkAssetId: { type: "string", description: "Linked payment asset ID" },
          linkAssetName: {
            type: "string",
            description: "Linked payment asset name",
          },
          jungsanDay: {
            type: "number",
            description: "Optional: Balance calculation day (1-31)",
          },
          paymentDay: {
            type: "number",
            description: "Optional: Payment due day (1-31)",
          },
        },
        required: ["assetId", "cardName", "linkAssetId", "linkAssetName"],
      },
    },
  • Internal registration of card_update handler in the toolHandlers object.
    card_update: handleCardUpdate,
  • TypeScript interface definition for CardUpdateInput, matching the Zod schema.
    /**
     * Input for updating a credit card
     */
    export interface CardUpdateInput {
      assetId: string;
      cardName: string;
      linkAssetId: string;
      linkAssetName: string;
      jungsanDay?: number;
      paymentDay?: 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 for behavioral disclosure. 'Modifies' implies a mutation operation, but it doesn't address critical aspects like required permissions, whether changes are reversible, potential side effects, error conditions, or what the response contains. This leaves significant gaps for a tool that alters financial 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, direct sentence with zero wasted words. It's perfectly front-loaded, immediately conveying the core purpose without any fluff or unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after modification, potential constraints, error handling, or relationship to other tools. Given the complexity of updating financial assets and the lack of structured behavioral information, this leaves too many unknowns for reliable agent 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%, so all parameters are documented in the schema itself. The description adds no additional parameter information beyond the general concept of modification. This meets the baseline expectation when the schema handles parameter documentation completely.

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 ('Modifies') and resource ('an existing credit card'), making the purpose immediately understandable. It distinguishes from siblings like card_create (creation) and card_list (listing), but doesn't specify what aspects of the card can be modified beyond the general concept.

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., needing an existing card), exclusions, or comparisons to sibling tools like asset_update or transaction_update, leaving the agent to infer usage context entirely from the tool name and schema.

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