Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

get_all_crypto

Read-only

Retrieve all cryptocurrency holdings, including both synced and manually managed assets.

Instructions

Get all cryptocurrency holdings from the v1 crypto endpoint. Returns both synced and manually managed crypto assets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for 'get_all_crypto'. It calls apiV1.get('/crypto') and returns the crypto assets data.
    async () => {
        try {
            const response = await apiV1.get("/crypto");
    
            if (!response.ok) {
                return handleApiError(
                    response,
                    "Failed to get crypto assets",
                );
            }
    
            const data: { crypto: CryptoAsset[] } = await response.json();
            return dataResponse(data);
        } catch (error) {
            return catchError(error, "Failed to get crypto assets");
        }
    },
  • Registration of the 'get_all_crypto' tool via server.registerTool() inside registerCryptoTools().
    export function registerCryptoTools(server: McpServer) {
        server.registerTool(
            "get_all_crypto",
            {
                description:
                    "Get all cryptocurrency holdings from the v1 crypto endpoint. Returns both synced and manually managed crypto assets.",
                annotations: {
                    readOnlyHint: true,
                },
            },
            async () => {
                try {
                    const response = await apiV1.get("/crypto");
    
                    if (!response.ok) {
                        return handleApiError(
                            response,
                            "Failed to get crypto assets",
                        );
                    }
    
                    const data: { crypto: CryptoAsset[] } = await response.json();
                    return dataResponse(data);
                } catch (error) {
                    return catchError(error, "Failed to get crypto assets");
                }
            },
        );
  • The CryptoAsset type used for the response schema of get_all_crypto.
    export interface CryptoAsset {
        id?: number | null;
        zabo_account_id?: number | null;
        source: "manual" | "synced";
        name: string;
        display_name: string | null;
        balance: string;
        balance_as_of?: string;
        currency: string;
        status: string;
        institution_name: string | null;
        created_at: string;
        to_base?: number | null;
    }
  • src/index.ts:14-33 (registration)
    Import and call of registerCryptoTools in the main server entry point.
    import { registerCryptoTools } from "./tools/crypto.js";
    import { registerPrompts } from "./prompts.js";
    
    const require = createRequire(import.meta.url);
    const { version } = require("../package.json");
    
    const server = new McpServer({
        name: "lunchmoney-mcp",
        version,
    });
    
    registerUserTools(server);
    registerCategoryTools(server);
    registerTagTools(server);
    registerTransactionTools(server);
    registerRecurringItemsTools(server);
    registerBudgetTools(server);
    registerManualAccountTools(server);
    registerPlaidAccountTools(server);
    registerCryptoTools(server);
  • apiV1 helper used by the handler to make the GET request to the v1 crypto endpoint.
    export const apiV1 = {
        get: (path: string) =>
            apiRequest("GET", path, undefined, "https://dev.lunchmoney.app/v1"),
        put: (path: string, body: unknown) =>
            apiRequest("PUT", path, body, "https://dev.lunchmoney.app/v1"),
    };
Behavior4/5

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

Annotations already mark it as readOnlyHint true, indicating no destructive actions. The description adds value by explaining the tool returns both synced and manually managed crypto assets, which is useful behavioral context beyond the annotations. No contradictions.

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 concise sentences with no redundancy. It front-loads the core purpose and adds a specific detail about asset types. Every word serves a purpose, making it highly efficient.

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

Completeness5/5

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

Given the tool has no parameters and no output schema, the description sufficiently explains what it returns (all crypto holdings, synced and manually managed). For a simple read-only list tool, this is complete. No additional context like pagination is required.

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?

The tool has zero parameters, and the input schema has 100% coverage (empty properties). The description does not add parameter information since none exist. Per guidelines, baseline is 4 for zero params, and no additional detail is needed.

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 tool retrieves all cryptocurrency holdings from the v1 crypto endpoint, specifying both synced and manually managed assets. This differentiates it from sibling tools like get_all_manual_accounts and get_all_plaid_accounts, providing a specific verb and resource.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use or not use this tool, nor does it mention alternatives. However, for a simple read-only list tool with no parameters, the usage context is implied by the name and purpose. No exclusions or comparisons are provided.

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