Tokenbooks - crypto and fiat accounting and payments

Preview Transaction Classification

preview_transaction_classification

Read-onlyIdempotent

Preview how selected wallet movements would be grouped and labeled as accounting transactions. Returns every proposal in order and saves nothing.

Input Schema

TableJSON Schema

Name	Required	Description
`operations`	Yes	Exact transfer-operation handles returned by transaction reads, including the accounting transaction each operation currently belongs to
`portfolioRef`	Yes	Portfolio name or slug inside that workspace. Call list_portfolios to resolve it.
`workspaceRef`	Yes	Workspace name or slug. Call list_workspaces to resolve it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`transactions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 20, 2026

changedInput schema / properties / portfolioRef / description

Previous value: -"Portfolio name or slug inside that workspace. Call list_portfolios, or find_portfolios when the user named one, to resolve it."New value: +"Portfolio name or slug inside that workspace. Call list_portfolios to resolve it."

changedInput schema / properties / workspaceRef / description

Previous value: -"Workspace name or slug. Call list_workspaces, or find_workspaces when the user named one, to resolve it."New value: +"Workspace name or slug. Call list_workspaces to resolve it."

Changed5 schema fields changedSep 17, 2026

addedInput schema / properties / operations / items / properties / portfolioTransactionId / description
```
Added value: +"Accounting transaction the movement currently belongs to."
```

addedInput schema / properties / operations / items / properties / txIndex / description

Added value: +"Position of the movement within that source transaction, from the same walletOperation."

addedInput schema / properties / operations / items / properties / walletTransactionId / description

Added value: +"Source transaction the wallet movement belongs to, from a walletOperation in a read tool result."

addedInput schema / properties / portfolioRef / description

Added value: +"Portfolio name or slug inside that workspace. Call list_portfolios, or find_portfolios when the user named one, to resolve it."

addedInput schema / properties / workspaceRef / description

Added value: +"Workspace name or slug. Call list_workspaces, or find_workspaces when the user named one, to resolve it."

Changed14 schema fields changedSep 15, 2026

changedInput schema / properties / operations / description

Previous value: -"Wallet operations to classify together as one transaction"New value: +"Exact transfer-operation handles returned by transaction reads, including the accounting transaction each operation currently belongs to"

addedInput schema / properties / operations / items / properties / portfolioTransactionId
```
Added value: +{
+  "minLength": 1,
+  "type": "string"
+}
```
removedInput schema / properties / operations / items / properties / txIndex / description
```
Removed value: -"Transfer index within the wallet transaction"
```
addedInput schema / properties / operations / items / properties / txIndex / maximum
```
Added value: +2147483647
```
addedInput schema / properties / operations / items / properties / txIndex / minimum
```
Added value: +0
```
removedInput schema / properties / operations / items / properties / walletTransactionId / description
```
Removed value: -"Wallet transaction handle (from a walletOperation)"
```
addedInput schema / properties / operations / items / properties / walletTransactionId / minLength
```
Added value: +1
```

changedInput schema / properties / operations / items / required

Previous value: -[
-  "walletTransactionId",
-  "txIndex"
-]New value: +[
+  "portfolioTransactionId",
+  "walletTransactionId",
+  "txIndex"
+]

addedInput schema / properties / operations / minItems
```
Added value: +1
```
removedInput schema / properties / portfolioRef / description
```
Removed value: -"Portfolio exact name or slug"
```
addedInput schema / properties / portfolioRef / minLength
```
Added value: +1
```
removedInput schema / properties / workspaceRef / description
```
Removed value: -"Workspace exact name or slug"
```
addedInput schema / properties / workspaceRef / minLength
```
Added value: +1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "transactions": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "operationType": {
+            "enum": [
+              "DEPOSIT_FIAT",
+              "INCOME",
+              "REFUND",
+              "WITHDRAWAL_FIAT",
+              "EXPENSE",
+              "BUY",
+              "SELL",
+              "EXCHANGE",
+              "SWAP",
+              "MOVE",
+              "INTERCOMPANY_SEND",
+              "INTERCOMPANY_RECEIVE",
+              "STAKE",
+              "UNSTAKE",
+              "PROTOCOL_DEPOSIT",
+              "PROTOCOL_WITHDRAW",
+              "VAULT_DEPOSIT",
+              "VAULT_WITHDRAW",
+              "LP_IN",
+              "LP_OUT",
+              "LOAN_BORROW",
+              "LOAN_REPAY",
+              "LOAN_LIQUIDATION",
+              "LEND_GIVE",
+              "LEND_WITHDRAW",
+              "ADJUSTMENT",
+              "UNCATEGORIZED",
+              "SPAM"
+            ],
+            "type": "string"
+          },
+          "operations": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "portfolioTransactionId": {
+                  "minLength": 1,
+                  "type": "string"
+                },
+                "txIndex": {
+                  "maximum": 2147483647,
+                  "minimum": 0,
+                  "type": "integer"
+                },
+                "walletTransactionId": {
+                  "minLength": 1,
+                  "type": "string"
+                }
+              },
+              "required": [
+                "portfolioTransactionId",
+                "walletTransactionId",
+                "txIndex"
+              ],
+              "type": "object"
+            },
+            "minItems": 1,
+            "type": "array"
+          },
+          "subType": {
+            "type": "string"
+          },
+          "systemNotes": {
+            "type": "string"
+          },
+          "timestamp": {
+            "format": "date-time",
+            "type": "string"
+          }
+        },
+        "required": [
+          "operationType",
+          "timestamp",
+          "operations"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "transactions"
+  ],
+  "type": "object"
+}

First observedSep 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: it promises ordered proposals and explicitly states that nothing is saved, reinforcing the non-destructive nature.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences carry complete intent with no filler. The action ('Preview') and key guarantee ('saves nothing') are front-loaded and every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a preview tool with full input-schema documentation, an output schema, and annotations covering safety and idempotency, the description is complete. An agent has enough to select and invoke it correctly without needing further context.

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%, with each parameter already documented, including resolution hints for portfolioRef and workspaceRef. The description itself adds little parameter-level meaning, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Preview how selected wallet movements would be grouped and labeled as accounting transactions.' It clearly communicates a non-committal, preview-only operation and distinguishes it from mutation tools like confirm_transaction or edit_transaction.

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?

The phrase 'saves nothing' strongly implies this tool is for inspection before a mutating counterpart such as confirm_transaction. It gives clear contextual guidance by emphasizing no persistence, though it does not explicitly name an alternative tool or exclusion condition.

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

All Tokenbooks - crypto and fiat accounting and payments tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?