Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

create_manual_account

Create a manually-managed account by providing type, name, and balance. Optionally set subtype, currency, institution, or closing date.

Instructions

Create a new manually-managed account. (Formerly create_asset.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesPrimary type of the manual account.
subtypeNoOptional subtype (e.g., retirement, checking, savings).
nameYesName of the account. 1-45 characters.
display_nameNoDisplay name. If unset, derived from institution_name and name.
balanceYesCurrent balance of the account.
balance_as_ofNoDate or datetime the balance is as of (ISO 8601).
currencyNoThree-letter lowercase currency code (defaults to primary currency).
institution_nameNoName of the institution holding the account.
closed_onNoDate the account was closed (YYYY-MM-DD). If set, status is forced to closed.
exclude_from_transactionsNoIf true, transactions cannot be assigned to this account.
Behavior2/5

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

Annotations provide only idempotentHint: false. Description lacks details about side effects, permissions, limits, or the nature of 'manually-managed'. It does not clarify behavior beyond creation.

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: one sentence plus a parentheses. It is front-loaded with the essential purpose and a rename note. Every word is earned.

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?

With 10 parameters, no output schema, and minimal description, the tool lacks return value details, field dependencies (e.g., balance_as_of with balance), and does not differentiate from the update sibling.

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 coverage is 100% with each parameter described. The description adds no extra meaning beyond the schema, so it meets the baseline.

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 action ('Create') and the resource ('manually-managed account'), with a note about legacy naming. It distinguishes from sibling tools like update_manual_account and delete_manual_account.

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?

No guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use, or conditions for use. The description simply states the action without context.

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/akutishevsky/lunchmoney-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server