Reads one transaction by transactionId for the authenticated user.
Use with an AI agent
Export this page as Markdown or bundle it with a task for your agent.
Try a task
Preview the prompt that will be copied
Access
- Effect: Read-only
- Required scope:
read(themcpscope also grants it)
Example request
The JSON-RPC message an MCP client sends to call this tool. Your client builds it for you; this is for reference and debugging in a tool such as MCP Inspector.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "read_transaction",
"arguments": {
"transactionId": "demo_transaction_01"
}
}
}Example IDs refer to fictional demo data. Replace them with IDs from your account before calling the real server.
Description
Reads one transaction by transactionId for the authenticated user.
Use this when you already have a transactionId (for example from create_transaction or list_transactions) and need full details before follow-up actions like deletion.
Set includeExactAmount when precision matters. When exactAmount is present, interpret its string units at the given decimal scale instead of rounding the legacy amount.
Temporal relativity tip: if the user says "the latest/last transaction" and you do not yet have a transactionId, first call list_transactions with limit=1 (default sort is newest first).
Context management tip: reuse transactionId from prior tool outputs whenever available instead of searching again.Input parameters
| Name | Type | Required | Description |
|---|---|---|---|
includeExactAmount | boolean | No | |
transactionId | string | Yes |
Full input schema (JSON Schema)
{
"additionalProperties": false,
"properties": {
"includeExactAmount": {
"type": "boolean"
},
"transactionId": {
"type": "string"
}
},
"required": [
"transactionId"
],
"type": "object"
}