Retrieve a specific scheduled transaction by ID to inspect upcoming bill or income details within a YNAB budget.
Get one scheduled transaction by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| budget_id | No | ||
| scheduled_transaction_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| scheduled_transaction | Yes |
Changes observed during successful MCP inspections.
v0.31.0Output schema / properties / scheduled_transaction / properties / amount / descriptionAdded value: +"Amount in decimal currency units"Output schema / properties / scheduled_transaction / properties / amount_currencyAdded value: +{
+ "type": "number"
+}Output schema / properties / scheduled_transaction / properties / amount_formattedAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / scheduled_transaction / properties / debt_transaction_typeAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / scheduled_transaction / properties / flag_nameAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / scheduled_transaction / properties / import_idAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / scheduled_transaction / properties / import_payee_nameAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / scheduled_transaction / properties / import_payee_name_originalAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / scheduled_transaction / properties / matched_transaction_idAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / scheduled_transaction / properties / parent_transaction_idAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / scheduled_transaction / properties / scheduled_transaction_idAdded value: +{
+ "type": "string"
+}Output schema / properties / scheduled_transaction / properties / subtransactionsAdded value: +{
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "amount": {
+ "description": "Amount in decimal currency units",
+ "type": "number"
+ },
+ "amount_currency": {
+ "type": "number"
+ },
+ "amount_formatted": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "amount_milliunits": {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ "category_id": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "category_name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "deleted": {
+ "type": "boolean"
+ },
+ "id": {
+ "type": "string"
+ },
+ "memo": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "payee_id": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "payee_name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "scheduled_transaction_id": {
+ "type": "string"
+ },
+ "transaction_id": {
+ "type": "string"
+ },
+ "transfer_account_id": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "transfer_transaction_id": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "amount"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+}Output schema / properties / scheduled_transaction / properties / transaction_idAdded value: +{
+ "type": "string"
+}Output schema / properties / scheduled_transaction / properties / transfer_account_idAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / scheduled_transaction / properties / transfer_transaction_idAdded value: +{
+ "type": [
+ "string",
+ "null"
+ ]
+}Output schema / properties / scheduled_transaction / properties / typeAdded value: +{
+ "enum": [
+ "transaction",
+ "subtransaction"
+ ],
+ "type": "string"
+}Output schema / properties / scheduled_transaction / requiredPrevious value: -[
- "id",
- "date_first",
- "date_next",
- "frequency",
- "amount",
- "amount_milliunits",
- "account_id",
- "account_name",
- "payee_id",
- "payee_name",
- "category_id",
- "category_name",
- "memo",
- "flag_color",
- "deleted"
-]New value: +[
+ "id",
+ "amount",
+ "deleted",
+ "account_id",
+ "date_first",
+ "date_next",
+ "frequency"
+]v0.29.1Output schema / properties / scheduled_transaction / properties / category_id / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / scheduled_transaction / properties / category_id / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / scheduled_transaction / properties / category_name / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / scheduled_transaction / properties / category_name / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / scheduled_transaction / properties / flag_color / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / scheduled_transaction / properties / flag_color / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / scheduled_transaction / properties / memo / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / scheduled_transaction / properties / memo / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / scheduled_transaction / properties / payee_id / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / scheduled_transaction / properties / payee_id / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / scheduled_transaction / properties / payee_name / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / scheduled_transaction / properties / payee_name / typeAdded value: +[
+ "string",
+ "null"
+]v0.27.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds nothing beyond that — no not-found behavior, no auth/scope notes, no mention of how the budget context is resolved.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler, so nothing is wasted. The terseness is efficient but leaves too little substance to call it exemplary.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained. Still, for a tool with two undocumented parameters and an unspecified not-found/error path, the description is too thin to let an agent call it correctly without trial and error.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description only hints that a scheduled_transaction_id identifies the record ("by ID"). The budget_id parameter is completely undefined in both schema and description, including whether it defaults to a configured budget.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ("Get one scheduled transaction") and the singular "one" implicitly distinguishes it from ynab_list_scheduled_transactions. It does not, however, explicitly name that sibling or contrast with the create/update/delete variants, leaving the agent to infer the boundary.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no when-to-use guidance, no prerequisites, and no alternatives. An agent must infer from the name alone that this is the single-record lookup path versus the list tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.