Tokenbooks - crypto and fiat accounting and payments

Create Portfolio

create_portfolio

Create an accounting portfolio in an existing workspace, optionally choosing jurisdiction and policies; Canada and US profiles require matching currency, entity type, and timezone. If no jurisdiction is selected, Tokenbooks uses generic accounting defaults. Search help for policy choices; workspace creation remains in the Tokenbooks UI.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Portfolio name
`currency`	No	Functional currency (default USD)
`workspaceRef`	Yes	Workspace name or slug. Call list_workspaces to resolve it.
`legalEntityType`	No	Legal entity classification for an explicit country profile
`jurisdictionCode`	No	Exact assigned ISO country code, or custom. If omitted, resolves Custom regardless of currency
`reportingTimezone`	No	Canonical IANA reporting timezone (default UTC)
`costBasisLotMethod`	No	Lot-matching method for disposals
`costBasisPerWallet`	No	Whether acquisition lots stay scoped to each wallet
`stablecoinTreatment`	No	Stablecoin valuation treatment; this does not change lot tracking
`gasFeeAccountingTreatment`	No	Accounting treatment for gas spend
`financialReportingFramework`	No	Financial reporting framework (default TAX_ONLY)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`slug`	Yes
`currency`	Yes
`createdAt`	Yes
`updatedAt`	Yes
`legalEntityType`	No
`hasPostedActivity`	Yes
`reportingTimezone`	Yes
`accountingConfiguration`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

addedOutput schema / properties / hasPostedActivity
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "slug",
-  "name",
-  "createdAt",
-  "updatedAt",
-  "currency",
-  "accountingConfiguration",
-  "reportingTimezone"
-]New value: +[
+  "slug",
+  "name",
+  "createdAt",
+  "updatedAt",
+  "currency",
+  "accountingConfiguration",
+  "reportingTimezone",
+  "hasPostedActivity"
+]

Changed2 schema fields changedSep 20, 2026

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."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "accountingConfiguration": {
+      "additionalProperties": false,
+      "properties": {
+        "baseCurrency": {
+          "type": "string"
+        },
+        "costBasisLotMethod": {
+          "enum": [
+            "FIFO",
+            "LIFO",
+            "HIFO",
+            "ACB"
+          ],
+          "type": "string"
+        },
+        "costBasisPerWallet": {
+          "type": "boolean"
+        },
+        "defiDepositTreatment": {
+          "enum": [
+            "TAXABLE_EXCHANGE",
+            "NON_TAXABLE_RESERVATION"
+          ],
+          "type": "string"
+        },
+        "financialReportingFramework": {
+          "default": "TAX_ONLY",
+          "enum": [
+            "TAX_ONLY",
+            "US_GAAP_PRE_2025",
+            "US_GAAP_ASC350_60",
+            "IFRS_IAS38",
+            "IFRS_IAS38_REVAL",
+            "IFRS_IAS2_LCNRV",
+            "IFRS_IAS2_BROKER_TRADER_FVLCTS",
+            "ASPE",
+            "FRS_102",
+            "AASB_138",
+            "OTHER"
+          ],
+          "type": "string"
+        },
+        "gasFeeAccountingTreatment": {
+          "enum": [
+            "DISPOSAL_AND_COST_BASIS",
+            "EXPENSE_ONLY"
+          ],
+          "type": "string"
+        },
+        "isPurchaseTaxable": {
+          "type": "boolean"
+        },
+        "jurisdictionCode": {
+          "type": "string"
+        },
+        "separateIncomeExpenseLines": {
+          "type": "boolean"
+        },
+        "stablecoinTreatment": {
+          "enum": [
+            "BASE",
+            "ASSET"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "gasFeeAccountingTreatment",
+        "isPurchaseTaxable",
+        "costBasisLotMethod",
+        "baseCurrency",
+        "jurisdictionCode",
+        "stablecoinTreatment",
+        "costBasisPerWallet",
+        "defiDepositTreatment",
+        "separateIncomeExpenseLines",
+        "financialReportingFramework"
+      ],
+      "type": "object"
+    },
+    "createdAt": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "legalEntityType": {
+      "enum": [
+        "BUSINESS",
+        "CORPORATION",
+        "INDIVIDUAL",
+        "TRUST",
+        "PARTNERSHIP"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "reportingTimezone": {
+      "type": "string"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "updatedAt": {
+      "format": "date-time",
+      "type": "string"
+    }
+  },
+  "required": [
+    "slug",
+    "name",
+    "createdAt",
+    "updatedAt",
+    "currency",
+    "accountingConfiguration",
+    "reportingTimezone"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 17, 2026

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."

First observedSep 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already disclose non-readOnly, non-idempotent, open-world, non-destructive nature. Description adds important behavioral constraints: US/Canada profiles require matching currency, entity type, and timezone, and omitted jurisdiction yields generic accounting defaults. It does not cover auth or return behavior, but output schema covers returns.

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?

Three sentences, front-loaded with the core action, then constraints and defaults, then help/UI note. No filler; every clause contributes useful context.

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

Completeness4/5

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

For an 11-parameter creation tool with 100% schema coverage, full annotations, and an output schema, the description covers purpose, key constraints, defaults, and where to find policy help. It could be richer about policy selection and prerequisites, but it is adequate for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds cross-field requirements (US/Canada need matching currency, entity type, and timezone) and default behavior for omitted jurisdiction, which goes beyond individual parameter docs. It also points to help for policy choices.

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?

States a specific verb and resource: 'Create an accounting portfolio in an existing workspace'. It scopes the operation and distinguishes it from read siblings like get_portfolio/list_portfolios, and explicitly notes that workspace creation remains in the UI.

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?

Provides clear context: an existing workspace is required, jurisdiction/policies are optional, and workspace creation must happen in the UI. It does not name alternative tools or explicitly say when to prefer this over get_portfolio, but the create verb makes usage evident.

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?