# read\_transaction

Reads one transaction by transactionId for the authenticated user.

Last updated October 1, 2026

## Access

*   Effect: **Read-only**
*   Required scope: `read` (the `mcp` scope 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.

```json
{
  "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)

```json
{
  "additionalProperties": false,
  "properties": {
    "includeExactAmount": {
      "type": "boolean"
    },
    "transactionId": {
      "type": "string"
    }
  },
  "required": [
    "transactionId"
  ],
  "type": "object"
}
```

Source: https://financesavi.com/developers/mcp/tools/read_transaction
