mmex-mcp

Overview Schema Source Related Servers Discussions Admin

mmex_payees_list

Retrieves all payees from a Money Manager EX database, providing a complete list of payment recipients for financial tracking.

Instructions

List all payees in the MMEX database.

    Args:
        db_path: Path to the .mmb database file. Optional if MMEX_DB_PATH env var is set.
        db_key: Encryption key for SQLCipher databases. Optional if MMEX_DB_KEY env var is set.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mmex_payees_list"
  }
}

Input Schema

Name	Required	Description	Default
`db_path`	No
`db_key`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 21, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, placing full burden on the description. The description only states it lists all payees, with no disclosure of behavioral traits such as read-only nature, performance implications, or required permissions. It does not describe what happens if the database is empty or if the query fails.

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: a single sentence for the purpose followed by parameter explanations in docstring format. No redundant information. Every word earns its place.

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 that there is an output schema (not shown) and the tool is a simple list, the description adequately covers the core functionality and parameters. It does not detail output structure, but the presence of an output schema compensates. It is sufficient for a straightforward read operation.

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 description coverage is 0%, so the description must compensate. It explains both parameters meaningfully: db_path is the path to the .mmb file (optional if env var set), and db_key is the encryption key (optional if env var set). This adds significant context beyond the schema's type and default.

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 'List all payees in the MMEX database.' It uses a specific verb ('list') and resource ('payees'), and the purpose is unambiguous. It differentiates from sibling tools like mmex_payees_get (single payee) and mmex_payees_create (creation).

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?

The description does not provide any explicit guidance on when to use this tool vs alternatives. It only states what it does, leaving the agent to infer usage context. No exclusions or prerequisites are mentioned.

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

Deploy Server