Skip to main content
Glama
akutishevsky

LunchMoney MCP Server

get_user

Read-only

Retrieve personal finance account details and user profile information for the authenticated user.

Instructions

Get details on the current user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Async handler that calls GET /me to fetch current user details, returns the User object via dataResponse.
    async () => {
        try {
            const response = await api.get("/me");
    
            if (!response.ok) {
                return handleApiError(response, "Failed to get user");
            }
    
            const user: User = await response.json();
    
            return dataResponse(user);
        } catch (error) {
            return catchError(error, "Failed to get user");
        }
    },
  • User interface defining the shape of the user object returned by the get_user tool.
    export interface User {
        id: number;
        name: string;
        email: string;
        account_id: number;
        budget_name: string;
        primary_currency: string;
        api_key_label: string | null;
    }
  • src/tools/user.ts:5-29 (registration)
    registerUserTools function that registers the get_user tool on the McpServer with description and readOnlyHint annotation.
    export function registerUserTools(server: McpServer) {
        server.registerTool(
            "get_user",
            {
                description: "Get details on the current user",
                annotations: {
                    readOnlyHint: true,
                },
            },
            async () => {
                try {
                    const response = await api.get("/me");
    
                    if (!response.ok) {
                        return handleApiError(response, "Failed to get user");
                    }
    
                    const user: User = await response.json();
    
                    return dataResponse(user);
                } catch (error) {
                    return catchError(error, "Failed to get user");
                }
            },
        );
  • src/index.ts:25-25 (registration)
    Call to registerUserTools(server) in the main entry point to wire up the get_user tool.
    registerUserTools(server);
  • dataResponse helper used by the get_user handler to format the User object as a text response.
    export function dataResponse(data: unknown) {
        return {
            content: [{ type: "text" as const, text: formatData(data) }],
        };
    }
Behavior2/5

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

The description only confirms the read-only nature, which is already indicated by the annotation `readOnlyHint: true`. It does not disclose what 'details' are returned (e.g., user ID, email), any authentication requirements, or potential limitations. The annotation lowers expectations but the description fails to add beyond that.

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 only six words, with no wasted content. It follows the standard verb-resource pattern and front-loads the key action. Every word contributes meaning.

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?

Despite having no parameters and a single annotation, the description is too sparse for an AI agent. It does not specify the structure of the returned details (e.g., fields like id, email, name). Without an output schema, the agent has no way to know what information to expect, which limits usability in automated workflows.

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?

There are no parameters (100% schema coverage trivially satisfied). With zero parameters, the baseline is 4; the description adds no parameter information but none is needed. It correctly implies no input is required.

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's purpose: retrieving details on the current user. The verb 'Get' and noun phrase 'details on the current user' are specific and unambiguous, distinguishing it from sibling tools that target other resources like categories or transactions.

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?

No explicit usage guidelines are provided. While the purpose is clear from the name and description, there is no mention of when to use this tool versus alternatives, nor any exclusions or prerequisites. For a simple no-parameter tool, this is minimally adequate but lacks guidance.

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