Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Createtransaction

createTransaction

Creates one or multiple transactions in a YNAB plan, including split transactions; future-dated scheduled transactions are not supported.

Instructions

Creates a single transaction or multiple transactions. If you provide a body containing a transaction object, a single transaction will be created and if you provide a body containing a transactions array, multiple transactions will be created. Scheduled transactions (transactions with a future date) cannot be created on this endpoint.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "createTransaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe id of the plan. "last-used" can be used to specify the last used plan and "default" can be used if default plan selection is enabled (see: https://api.ynab.com/#oauth-default-plan).
transactionNo
transactionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / transaction / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "account_id": {
      -        "format": "uuid",
      -        "type": "string"
      -      },
      -      "amount": {
      -        "description": "The transaction amount in milliunits format.  Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored.",
      -        "format": "int64",
      -        "type": "integer"
      -      },
      -      "approved": {
      -        "description": "Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default.",
      -        "type": "boolean"
      -      },
      -      "category_id": {
      -        "description": "The category for the transaction.  To configure a split transaction, you can specify null for `category_id` and provide a `subtransactions` array as part of the transaction object.  If an existing transaction is a split, the `category_id` cannot be changed.  Credit Card Payment categories are not permitted and will be ignored if supplied.",
      -        "format": "uuid",
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "cleared": {
      -        "description": "The cleared status of the transaction",
      -        "enum": [
      -          "cleared",
      -          "uncleared",
      -          "reconciled"
      -        ],
      -        "type": "string"
      -      },
      -      "date": {
      -        "description": "The transaction date in ISO format (e.g. 2016-12-01).  Future dates (scheduled transactions) are not permitted.  Split transaction dates cannot be changed and if a different date is supplied it will be ignored.",
      -        "format": "date",
      -        "type": "string"
      -      },
      -      "flag_color": {
      -        "description": "The transaction flag",
      -        "enum": [
      -          "red",
      -          "orange",
      -          "yellow",
      -          "green",
      -          "blue",
      -          "purple",
      -          "",
      -          null
      -        ],
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "memo": {
      -        "maxLength": 500,
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "payee_id": {
      -        "description": "The payee for the transaction.  To create a transfer between two accounts, use the account transfer payee pointing to the target account.  Account transfer payees are specified as `transfer_payee_id` on the account resource.",
      -        "format": "uuid",
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "payee_name": {
      -        "description": "The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if `import_id` is also specified) or (2) a payee with the same name or (3) creation of a new payee.",
      -        "maxLength": 200,
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "subtransactions": {
      -        "description": "An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported.",
      -        "items": {
      -          "properties": {
      -            "amount": {
      -              "description": "The subtransaction amount in milliunits format.",
      -              "format": "int64",
      -              "type": "integer"
      -            },
      -            "category_id": {
      -              "description": "The category for the subtransaction.  Credit Card Payment categories are not permitted and will be ignored if supplied.",
      -              "format": "uuid",
      -              "type": [
      -                "string",
      -                "null"
      -              ]
      -            },
      -            "memo": {
      -              "maxLength": 500,
      -              "type": [
      -                "string",
      -                "null"
      -              ]
      -            },
      -            "payee_id": {
      -              "description": "The payee for the subtransaction.",
      -              "format": "uuid",
      -              "type": [
      -                "string",
      -                "null"
      -              ]
      -            },
      -            "payee_name": {
      -              "description": "The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if import_id is also specified on parent transaction) or (2) a payee with the same name or (3) creation of a new payee.",
      -              "maxLength": 200,
      -              "type": [
      -                "string",
      -                "null"
      -              ]
      -            }
      -          },
      -          "required": [
      -            "amount"
      -          ],
      -          "type": "object"
      -        },
      -        "type": "array"
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "properties": {
      -      "import_id": {
      -        "description": "If specified, a new transaction will be assigned this `import_id` and considered \"imported\".  We will also attempt to match this imported transaction to an existing \"user-entered\" transaction on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'.  If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.  Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).",
      -        "maxLength": 36,
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "account_id": {
      +        "format": "uuid",
      +        "type": "string"
      +      },
      +      "amount": {
      +        "description": "The transaction amount in milliunits format.  Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored.",
      +        "format": "int64",
      +        "type": "integer"
      +      },
      +      "approved": {
      +        "description": "Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default.",
      +        "type": "boolean"
      +      },
      +      "category_id": {
      +        "description": "The category for the transaction.  To configure a split transaction, you can specify null for `category_id` and provide a `subtransactions` array as part of the transaction object.  If an existing transaction is a split, the `category_id` cannot be changed.  Credit Card Payment categories are not permitted and will be ignored if supplied.",
      +        "format": "uuid",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "cleared": {
      +        "description": "The cleared status of the transaction",
      +        "enum": [
      +          "cleared",
      +          "uncleared",
      +          "reconciled"
      +        ],
      +        "type": "string"
      +      },
      +      "date": {
      +        "description": "The transaction date in ISO format (e.g. 2016-12-01).  Future dates (scheduled transactions) are not permitted.  Split transaction dates cannot be changed and if a different date is supplied it will be ignored.",
      +        "format": "date",
      +        "type": "string"
      +      },
      +      "flag_color": {
      +        "description": "The transaction flag",
      +        "enum": [
      +          "red",
      +          "orange",
      +          "yellow",
      +          "green",
      +          "blue",
      +          "purple",
      +          "",
      +          null
      +        ],
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "memo": {
      +        "maxLength": 500,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "payee_id": {
      +        "description": "The payee for the transaction.  To create a transfer between two accounts, use the account transfer payee pointing to the target account.  Account transfer payees are specified as `transfer_payee_id` on the account resource.",
      +        "format": "uuid",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "payee_name": {
      +        "description": "The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if `import_id` is also specified) or (2) a payee with the same name or (3) creation of a new payee.",
      +        "maxLength": 200,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "subtransactions": {
      +        "description": "An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported and will return an error.  Splits are not allowed on tracking accounts or on transfers between on-budget accounts; a transfer to a tracking account can be a split.",
      +        "items": {
      +          "properties": {
      +            "amount": {
      +              "description": "The subtransaction amount in milliunits format.",
      +              "format": "int64",
      +              "type": "integer"
      +            },
      +            "category_id": {
      +              "description": "The category for the subtransaction.  Credit Card Payment categories are not permitted and will be ignored if supplied.",
      +              "format": "uuid",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "memo": {
      +              "maxLength": 500,
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "payee_id": {
      +              "description": "The payee for the subtransaction.",
      +              "format": "uuid",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "payee_name": {
      +              "description": "The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if import_id is also specified on parent transaction) or (2) a payee with the same name or (3) creation of a new payee.",
      +              "maxLength": 200,
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "required": [
      +            "amount"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "properties": {
      +      "import_id": {
      +        "description": "If specified, a new transaction will be assigned this `import_id` and considered \"imported\".  We will also attempt to match this imported transaction to an existing \"user-entered\" transaction on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'.  If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.  Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).",
      +        "maxLength": 36,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  }
      +]
    • changedInput schema / properties / transactions / items / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "account_id": {
      -        "format": "uuid",
      -        "type": "string"
      -      },
      -      "amount": {
      -        "description": "The transaction amount in milliunits format.  Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored.",
      -        "format": "int64",
      -        "type": "integer"
      -      },
      -      "approved": {
      -        "description": "Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default.",
      -        "type": "boolean"
      -      },
      -      "category_id": {
      -        "description": "The category for the transaction.  To configure a split transaction, you can specify null for `category_id` and provide a `subtransactions` array as part of the transaction object.  If an existing transaction is a split, the `category_id` cannot be changed.  Credit Card Payment categories are not permitted and will be ignored if supplied.",
      -        "format": "uuid",
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "cleared": {
      -        "description": "The cleared status of the transaction",
      -        "enum": [
      -          "cleared",
      -          "uncleared",
      -          "reconciled"
      -        ],
      -        "type": "string"
      -      },
      -      "date": {
      -        "description": "The transaction date in ISO format (e.g. 2016-12-01).  Future dates (scheduled transactions) are not permitted.  Split transaction dates cannot be changed and if a different date is supplied it will be ignored.",
      -        "format": "date",
      -        "type": "string"
      -      },
      -      "flag_color": {
      -        "description": "The transaction flag",
      -        "enum": [
      -          "red",
      -          "orange",
      -          "yellow",
      -          "green",
      -          "blue",
      -          "purple",
      -          "",
      -          null
      -        ],
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "memo": {
      -        "maxLength": 500,
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "payee_id": {
      -        "description": "The payee for the transaction.  To create a transfer between two accounts, use the account transfer payee pointing to the target account.  Account transfer payees are specified as `transfer_payee_id` on the account resource.",
      -        "format": "uuid",
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "payee_name": {
      -        "description": "The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if `import_id` is also specified) or (2) a payee with the same name or (3) creation of a new payee.",
      -        "maxLength": 200,
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "subtransactions": {
      -        "description": "An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported.",
      -        "items": {
      -          "properties": {
      -            "amount": {
      -              "description": "The subtransaction amount in milliunits format.",
      -              "format": "int64",
      -              "type": "integer"
      -            },
      -            "category_id": {
      -              "description": "The category for the subtransaction.  Credit Card Payment categories are not permitted and will be ignored if supplied.",
      -              "format": "uuid",
      -              "type": [
      -                "string",
      -                "null"
      -              ]
      -            },
      -            "memo": {
      -              "maxLength": 500,
      -              "type": [
      -                "string",
      -                "null"
      -              ]
      -            },
      -            "payee_id": {
      -              "description": "The payee for the subtransaction.",
      -              "format": "uuid",
      -              "type": [
      -                "string",
      -                "null"
      -              ]
      -            },
      -            "payee_name": {
      -              "description": "The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if import_id is also specified on parent transaction) or (2) a payee with the same name or (3) creation of a new payee.",
      -              "maxLength": 200,
      -              "type": [
      -                "string",
      -                "null"
      -              ]
      -            }
      -          },
      -          "required": [
      -            "amount"
      -          ],
      -          "type": "object"
      -        },
      -        "type": "array"
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "properties": {
      -      "import_id": {
      -        "description": "If specified, a new transaction will be assigned this `import_id` and considered \"imported\".  We will also attempt to match this imported transaction to an existing \"user-entered\" transaction on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'.  If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.  Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).",
      -        "maxLength": 36,
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "account_id": {
      +        "format": "uuid",
      +        "type": "string"
      +      },
      +      "amount": {
      +        "description": "The transaction amount in milliunits format.  Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored.",
      +        "format": "int64",
      +        "type": "integer"
      +      },
      +      "approved": {
      +        "description": "Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default.",
      +        "type": "boolean"
      +      },
      +      "category_id": {
      +        "description": "The category for the transaction.  To configure a split transaction, you can specify null for `category_id` and provide a `subtransactions` array as part of the transaction object.  If an existing transaction is a split, the `category_id` cannot be changed.  Credit Card Payment categories are not permitted and will be ignored if supplied.",
      +        "format": "uuid",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "cleared": {
      +        "description": "The cleared status of the transaction",
      +        "enum": [
      +          "cleared",
      +          "uncleared",
      +          "reconciled"
      +        ],
      +        "type": "string"
      +      },
      +      "date": {
      +        "description": "The transaction date in ISO format (e.g. 2016-12-01).  Future dates (scheduled transactions) are not permitted.  Split transaction dates cannot be changed and if a different date is supplied it will be ignored.",
      +        "format": "date",
      +        "type": "string"
      +      },
      +      "flag_color": {
      +        "description": "The transaction flag",
      +        "enum": [
      +          "red",
      +          "orange",
      +          "yellow",
      +          "green",
      +          "blue",
      +          "purple",
      +          "",
      +          null
      +        ],
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "memo": {
      +        "maxLength": 500,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "payee_id": {
      +        "description": "The payee for the transaction.  To create a transfer between two accounts, use the account transfer payee pointing to the target account.  Account transfer payees are specified as `transfer_payee_id` on the account resource.",
      +        "format": "uuid",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "payee_name": {
      +        "description": "The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if `import_id` is also specified) or (2) a payee with the same name or (3) creation of a new payee.",
      +        "maxLength": 200,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "subtransactions": {
      +        "description": "An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported and will return an error.  Splits are not allowed on tracking accounts or on transfers between on-budget accounts; a transfer to a tracking account can be a split.",
      +        "items": {
      +          "properties": {
      +            "amount": {
      +              "description": "The subtransaction amount in milliunits format.",
      +              "format": "int64",
      +              "type": "integer"
      +            },
      +            "category_id": {
      +              "description": "The category for the subtransaction.  Credit Card Payment categories are not permitted and will be ignored if supplied.",
      +              "format": "uuid",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "memo": {
      +              "maxLength": 500,
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "payee_id": {
      +              "description": "The payee for the subtransaction.",
      +              "format": "uuid",
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "payee_name": {
      +              "description": "The payee name.  If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if import_id is also specified on parent transaction) or (2) a payee with the same name or (3) creation of a new payee.",
      +              "maxLength": 200,
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "required": [
      +            "amount"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "properties": {
      +      "import_id": {
      +        "description": "If specified, a new transaction will be assigned this `import_id` and considered \"imported\".  We will also attempt to match this imported transaction to an existing \"user-entered\" transaction on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'.  If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.  Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).",
      +        "maxLength": 36,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  }
      +]
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose one important behavioral constraint (no future-dated transactions) and the single-vs-bulk fan-out. It says nothing about permissions/plan scoping, idempotency or duplicate risk on bulk submits, partial-failure behavior in the array case, or what the call returns.

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?

Three front-loaded sentences with no filler; the mode distinction comes first and the date restriction last. The single/multiple rule is restated slightly twice, but nothing is wasteful enough to obscure the point.

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 3-parameter mutation tool with a deeply nested payload and no output schema, the description covers the two most decision-relevant facts (which body key selects which mode, and the no-future-date rule). It omits error/validation behavior and the response shape, leaving real gaps for an agent submitting bulk arrays.

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?

Top-level schema description coverage is reported at 33%, but the nested transaction schema is extremely well documented, so the schema does most of the work. The description's real contribution is clarifying that `transaction` and `transactions` are alternative body shapes rather than co-required fields — meaningful, but it does not state what happens if both or neither are supplied.

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?

The description opens with a specific verb and resource ('Creates a single transaction or multiple transactions'), which cleanly separates it from the updateTransaction, deleteTransaction, and createScheduledTransaction siblings. It does not name a sibling to route against, but the create semantics are unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit negative condition ('Scheduled transactions (transactions with a future date) cannot be created on this endpoint') and explains the mutually exclusive modes: a `transaction` object for one, a `transactions` array for many. It stops short of naming createScheduledTransaction as the alternative, so the routing hint is implied rather than stated.

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