Skip to main content
Glama
shahlaukik

Money Manager MCP Server

by shahlaukik

asset_update

Update existing financial assets in your Money Manager account to maintain accurate tracking of balances, names, groups, and linked assets.

Instructions

Modifies an existing asset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetIdYesAsset ID
assetGroupIdYesAsset group ID
assetGroupNameYesAsset group name
assetNameYesAsset name
assetMoneyYesCurrent balance
linkAssetIdNoOptional: Linked asset ID
linkAssetNameNoOptional: Linked asset name

Implementation Reference

  • Handler function that validates input and calls the Money Manager /assetModify API to update an asset.
    /**
     * Handler for asset_update tool
     * Modifies an existing asset
     */
    export async function handleAssetUpdate(
      httpClient: HttpClient,
      input: unknown,
    ): Promise<AssetOperationResponse> {
      const validated = AssetUpdateInputSchema.parse(input);
    
      const response = await httpClient.post<ApiOperationResponse>("/assetModify", {
        assetId: validated.assetId,
        assetGroupId: validated.assetGroupId,
        assetGroupName: validated.assetGroupName,
        assetName: validated.assetName,
        assetMoney: validated.assetMoney,
        linkAssetId: validated.linkAssetId || "",
        linkAssetName: validated.linkAssetName || "",
      });
    
      return {
        success: response.success !== false && response.result !== "fail",
        assetId: validated.assetId,
        message: response.message,
      };
    }
  • Zod schema defining the input structure and validation for the asset_update tool.
     * Input schema for asset_update tool
     */
    export const AssetUpdateInputSchema = z.object({
      assetId: AssetIdSchema,
      assetGroupId: NonEmptyString,
      assetGroupName: NonEmptyString,
      assetName: NonEmptyString,
      assetMoney: z.number(),
      linkAssetId: z.string().optional(),
      linkAssetName: z.string().optional(),
    });
    
    export type AssetUpdateInput = z.infer<typeof AssetUpdateInputSchema>;
  • Registration of asset_update handler in the toolHandlers map used by executeToolHandler.
    // Assets
    asset_list: handleAssetList,
    asset_create: handleAssetCreate,
    asset_update: handleAssetUpdate,
    asset_delete: handleAssetDelete,
  • src/index.ts:246-274 (registration)
    MCP protocol tool definition registration including name, description, and JSON input schema.
    {
      name: "asset_update",
      description: "Modifies an existing asset.",
      inputSchema: {
        type: "object" as const,
        properties: {
          assetId: { type: "string", description: "Asset ID" },
          assetGroupId: { type: "string", description: "Asset group ID" },
          assetGroupName: { type: "string", description: "Asset group name" },
          assetName: { type: "string", description: "Asset name" },
          assetMoney: { type: "number", description: "Current balance" },
          linkAssetId: {
            type: "string",
            description: "Optional: Linked asset ID",
          },
          linkAssetName: {
            type: "string",
            description: "Optional: Linked asset name",
          },
        },
        required: [
          "assetId",
          "assetGroupId",
          "assetGroupName",
          "assetName",
          "assetMoney",
        ],
      },
    },
  • TypeScript type definition for asset update input parameters.
    /**
     * Input for updating an asset
     */
    export interface AssetUpdateInput extends AssetCreateInput {
      assetId: string;
    }
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 disclose whether this requires specific permissions, whether changes are reversible, what happens to unspecified fields, or any rate limits/constraints. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 three words ('Modifies an existing asset'), with zero wasted language. It's front-loaded with the core action and resource. While arguably too brief for a mutation tool with no annotations, it earns full marks for conciseness as every word serves a purpose.

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 7 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what 'modifies' entails, what fields are updatable, what permissions are needed, or what the response contains. The agent would need to infer too much from the parameter names alone, making this description inadequate for the tool's complexity.

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 7 parameters with basic descriptions. The description adds no additional parameter semantics beyond the generic 'modifies an existing asset' statement. This meets the baseline of 3 when schema coverage is high, but doesn't provide extra value like explaining relationships between parameters or usage patterns.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Modifies an existing asset' clearly states the action (modifies) and resource (asset), distinguishing it from create/delete operations. However, it doesn't specify what aspects of an asset can be modified or how this differs from other update tools like card_update or transaction_update, making it somewhat vague about its specific scope.

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 like asset_create or asset_delete, nor does it mention prerequisites such as needing an existing asset ID. While the required parameters imply assetId must be provided, there's no explicit usage context or exclusions stated in the description itself.

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