Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_get_transaction

Read-only

Retrieve a single YNAB transaction with full details—IDs, import info, and splits—by providing a transaction ID.

Instructions

Get one transaction in full, including ids, import details and splits.

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": {
      "transaction_id": "<transaction_id>"
    },
    "name": "ynab_get_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idNoPlan (budget) id from ynab_list_plans. Omit to use the configured default plan.
transaction_idYesTransaction id from ynab_list_transactions.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds modest behavioral value by naming what the payload contains (ids, import details, splits), but says nothing about errors, missing-id behavior, or freshness beyond what annotations and the output schema supply.

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?

A single front-loaded sentence with no filler; every clause ('one', 'in full', 'including ids, import details and splits') carries information. It is arguably too terse for a tool with a sibling list counterpart, but nothing is wasted.

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 an output schema handling return structure and 100% schema coverage for the two parameters, the description only needs to state what the tool fetches, which it does. The remaining gap is routing guidance versus the list and scheduled-transaction siblings, which is a minor but real omission.

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 transaction_id and plan_id are already fully documented, including the 'from ynab_list_transactions' provenance and the default-plan fallback. The description adds no meaning beyond that, which is the baseline case for a 3.

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 ('Get one transaction in full'), and the words 'one' and 'in full' distinguish it from the list-style siblings such as ynab_list_transactions. It does not explicitly name an alternative, but the retrieval scope is unambiguous.

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 only implied: 'in full' signals this is the detail view rather than the list view, and the schema notes the id comes from ynab_list_transactions. The description itself offers no explicit when-to-use or when-not guidance and never mentions ynab_get_scheduled_transaction, which is the closest source of confusion.

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