Skip to main content
Glama
moneylover-mcp

moneylover-mcp

Get Categories

get_categories

Lists categories for a specified wallet and returns their wallet-specific IDs, helping you choose the right category before adding a transaction.

Instructions

List categories for a wallet. Note: the ids returned here are wallet-specific; add_transaction translates them to global ids automatically.

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": {
      "walletId": "<walletId>"
    },
    "name": "get_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoJWT token returned by login, or derived from environment credentials
walletIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does surface a genuinely important trait: returned ids are wallet-specific and add_transaction translates them automatically. It does not state that this is a read-only operation, how authentication works via the token, or whether the list is paginated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and followed by the one caveat that actually matters. No filler or redundant restatement of the name.

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?

For a simple two-parameter lister with no output schema, the description covers the core action and the id-translation caveat. It leaves open what a category record contains (name, type, parent) and how walletId is obtained, which an agent would still need to infer.

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 50%: the token parameter is documented, while walletId is not. The phrase "for a wallet" implies walletId selects the category namespace and the id note clarifies the meaning of the response ids, but no format or sourcing details are added for the undocumented parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List categories for a wallet" gives a specific verb and resource with a clear scope, and no sibling tool offers a competing category listing, so the agent can distinguish it easily. It stops short of a 5 only because it does not contrast itself with any sibling.

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?

Usage is implied: call this to enumerate categories before adding a transaction. The note about add_transaction translates ids hints at the workflow, but there is no explicit when-to-use/when-not guidance or stated prerequisites (e.g., obtaining walletId from get_wallets).

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