Money Lover MCP Server

Login to Money Lover

login

Authenticate to Money Lover using email and password to obtain a JWT token for accessing personal finance data through the MCP server.

Instructions

Authenticate using Money Lover credentials to retrieve a JWT token.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>",
      "password": "<password>"
    },
    "name": "login"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes	Money Lover account email
`password`	Yes	Money Lover account password

Output Schema

Name	Required	Description	Default
`token`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.3Apr 19, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. Describes retrieving a token but does not disclose side effects or that the token should be stored for subsequent requests.

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?

Single sentence with no unnecessary words. Perfectly concise.

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

Completeness3/5

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

Output schema exists but description does not mention that the token must be used for authorization in other endpoints. Missing context for the authentication flow.

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 clear descriptions for both parameters. Description adds no additional meaning beyond the schema.

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?

Description clearly states the action (authenticate), resource (Money Lover credentials), and output (JWT token). Distinguishes from sibling tools that handle transactions, categories, etc.

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?

Implied that this is the authentication step before using other tools, but no explicit guidance on when to use, prerequisites, or alternatives. Could be more helpful.

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