Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_list_scheduled_transactions

Read-only

List scheduled recurring or future transactions in soonest-first order to track upcoming bills and plan cash flow; filter by plan, account, category, or due date.

Instructions

List scheduled (recurring or future) transactions, soonest first. Useful for upcoming bills.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return.
offsetNoRows to skip (use next_offset from a prior call).
plan_idNoPlan (budget) id from ynab_list_plans. Omit to use the configured default plan.
account_idNoOnly this account.
due_beforeNoOnly those whose next date is on/before this date (YYYY-MM-DD).
category_idNoOnly this category.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds the ordering guarantee ('soonest first'), which is genuinely useful, but says nothing about pagination behavior despite limit/offset parameters.

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 resource and ordering rule. The trailing 'Useful for upcoming bills' is mild filler but does convey intent efficiently.

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 and a fully documented 6-parameter schema carry most of the burden, but the description omits how results differ from actual transactions and says nothing about paginating with limit/offset for accounts with many scheduled items.

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%, so every parameter including plan_id, due_before, and offset is already documented. The description adds no filter or pagination semantics beyond what the schema provides, so baseline 3 applies.

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 and resource ('List scheduled transactions') and clarifies scope with '(recurring or future)', which separates it from the sibling ynab_list_transactions. It does not explicitly name the alternative, but the parenthetical resolves the ambiguity.

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?

'Useful for upcoming bills' hints at a use case but gives no explicit when-to-use vs. when-not, and never points to ynab_list_transactions or ynab_get_scheduled_transaction as alternatives.

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