Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

list_uncategorized_transactions

Lists transactions missing a category so they can be reviewed and categorized; split transactions include each portion's category and amount.

Instructions

Lists transactions that don't yet have a category assigned, so they can be reviewed and categorized. Split transactions include a 'splits' array showing each portion's category and amount.

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": "list_uncategorized_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_idNoThe budget ID, or 'last-used' for the most recently used budget.last-used

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.9.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the return shape for split transactions ('splits' array with category and amount per portion), which is real behavioral context, but it says nothing about ordering, pagination, result limits, or the fact that this is a read-only operation.

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?

Two sentences, both front-loaded: the filter definition comes first and the output-shape note second. No filler or restatement of the tool name.

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?

With no output schema, the description's note about the 'splits' array is the only place return structure is documented, which is a meaningful contribution. It is nearly complete for a simple one-parameter list tool, with only ordering/pagination left unstated.

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 description coverage is 100% for the single budget_id parameter, including the 'last-used' default, so the schema already documents it fully. The description adds no additional meaning about scoping or default behavior beyond what the schema states.

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?

States a specific verb ('Lists') and resource ('transactions') with a precise filter: those without a category assigned. This distinguishes it from 'list_unapproved_transactions' and 'search_transactions' by the filter condition itself, though it never names an alternative explicitly.

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 phrase 'so they can be reviewed and categorized' implies the workflow context (a precursor to categorize_transaction or bulk_suggest_categories), but no tool is named and there is no explicit when-not guidance. Usage is inferable rather than stated.

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