Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

by akutishevsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_manual_crypto

Idempotent

Update a manually-managed crypto balance by changing its name, display name, institution, or balance. Specify the crypto ID to select the asset.

Instructions

Update a manually-managed crypto balance. At least one of name, display_name, institution_name, or balance must be supplied. The symbol of an existing balance cannot be changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew name for the crypto asset.
balanceNoNew balance as a numeric string with up to 18 decimal places. Pass a string to avoid losing precision.
crypto_idYesId of the manual crypto balance to update. Synced crypto balances cannot be updated.
display_nameNoNew display name for the crypto asset. Pass null to clear it.
institution_nameNoNew institution or wallet provider display name. Pass null to clear it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv1.0.5
    • addedInput schema / properties / balance / anyOf
      Added value: +[
+  {
+    "pattern": "^-?\\d+(\\.\\d{1,18})?$",
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]
    • changedInput schema / properties / balance / description
      Previous value: -"Updated balance of the crypto account."New value: +"New balance as a numeric string with up to 18 decimal places. Pass a string to avoid losing precision."
    • removedInput schema / properties / balance / type
      Removed value: -"number"
    • changedInput schema / properties / crypto_id / description
      Previous value: -"ID of the manual crypto asset to update. Synced crypto assets cannot be updated."New value: +"Id of the manual crypto balance to update. Synced crypto balances cannot be updated."
    • changedInput schema / properties / crypto_id / type
      Previous value: -"number"New value: +"integer"
    • removedInput schema / properties / currency
      Removed value: -{
-  "description": "Optional supported cryptocurrency code.",
-  "type": "string"
-}
    • addedInput schema / properties / display_name / anyOf
      Added value: +[
+  {
+    "maxLength": 45,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / display_name / description
      Previous value: -"Optional display name for the account."New value: +"New display name for the crypto asset. Pass null to clear it."
    • removedInput schema / properties / display_name / maxLength
      Removed value: -25
    • removedInput schema / properties / display_name / type
      Removed value: -"string"
    • addedInput schema / properties / institution_name / anyOf
      Added value: +[
+  {
+    "maxLength": 50,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / institution_name / description
      Previous value: -"Optional provider that holds the asset."New value: +"New institution or wallet provider display name. Pass null to clear it."
    • removedInput schema / properties / institution_name / maxLength
      Removed value: -50
    • removedInput schema / properties / institution_name / type
      Removed value: -"string"
    • changedInput schema / properties / name / description
      Previous value: -"Optional official or full name of the account."New value: +"New name for the crypto asset."
    • addedInput schema / properties / name / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
-  "crypto_id",
-  "balance"
-]New value: +[
+  "crypto_id"
+]
  2. Addedv1.0.3
  3. Removedv1.0.2
  4. Changed10 schema fields changedv1.0.1
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / balance
      Added value: +{
+  "description": "Updated balance of the crypto account.",
+  "type": "number"
+}
    • addedInput schema / properties / crypto_id
      Added value: +{
+  "description": "ID of the manual crypto asset to update. Synced crypto assets cannot be updated.",
+  "type": "number"
+}
    • addedInput schema / properties / currency
      Added value: +{
+  "description": "Optional supported cryptocurrency code.",
+  "type": "string"
+}
    • addedInput schema / properties / display_name
      Added value: +{
+  "description": "Optional display name for the account.",
+  "maxLength": 25,
+  "type": "string"
+}
    • removedInput schema / properties / input
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "balance": {
-      "description": "Updated balance of the crypto asset",
-      "type": "number"
-    },
-    "crypto_id": {
-      "description": "ID of the crypto asset to update",
-      "type": "number"
-    }
-  },
-  "required": [
-    "crypto_id"
-  ],
-  "type": "object"
-}
    • addedInput schema / properties / institution_name
      Added value: +{
+  "description": "Optional provider that holds the asset.",
+  "maxLength": 50,
+  "type": "string"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Optional official or full name of the account.",
+  "maxLength": 45,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "input"
-]New value: +[
+  "crypto_id",
+  "balance"
+]
  5. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

The annotation idempotentHint=true already conveys idempotency. The description adds useful constraints: 'At least one of... must be supplied' and 'The symbol... cannot be changed.' These are not in the annotations and add value. However, the description does not disclose other behaviors such as error handling or whether omitted fields retain their values, which leaves some 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 two sentences, each essential. It front-loads the purpose and immediately gives the critical 'at least one' requirement and the symbol immutability constraint. No word is wasted.

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?

Given the tool's moderate complexity (5 params, 1 required, idempotentHint), the description covers the main purpose, the validation rule, and a key behavioral limitation. It doesn't mention that omitted fields remain unchanged, but the schema's null descriptions and partial-update phrasing imply it. With no output schema, this is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed parameter descriptions, so baseline is 3. The description adds a crucial cross-parameter rule not in the schema: at least one of name, display_name, institution_name, or balance must be supplied. This goes beyond the schema's required crypto_id and clarifies validation logic.

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 states 'Update a manually-managed crypto balance,' which clearly identifies the action and resource. It distinguishes from sibling tools like create/delete/get manual crypto and from synced crypto tools. The added constraints about required fields and immutable symbol further clarify its role.

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

Usage Guidelines4/5

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

The phrase 'manually-managed' sets a clear context for when to use this tool. It doesn't explicitly name alternatives or exclusions, but the resource type is unambiguous. The schema's crypto_id description also notes that synced crypto cannot be updated, reinforcing the manual-only scope.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools