Tokenbooks - crypto and fiat accounting and payments

Get Portfolio Balances

get_portfolio_balances

Read-onlyIdempotent

Check whether each wallet's computed token balances match its latest synchronized snapshot; returns per-wallet match status, token count, last transaction time, and an overall match flag.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`portfolioRef`	Yes	Portfolio exact name or slug
`workspaceRef`	Yes	Workspace exact name or slug

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`allBalancesMatch`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "allBalancesMatch": {
+      "type": "boolean"
+    },
+    "data": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "address": {
+            "type": "string"
+          },
+          "chainId": {
+            "type": "string"
+          },
+          "isBalanceMatch": {
+            "type": "boolean"
+          },
+          "lastTransactionTimestamp": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "tokenCount": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          }
+        },
+        "required": [
+          "chainId",
+          "address",
+          "isBalanceMatch",
+          "tokenCount"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "data",
+    "allBalancesMatch"
+  ],
+  "type": "object"
+}

First observedSep 14, 2026

TDQS

A4/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. The description adds meaningful behavioral context by explaining the comparison against the latest synchronized snapshot and enumerating the returned per-wallet fields, using non-mutating language.

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?

The description is a single sentence that front-loads the core purpose and immediately lists the returned output. Every clause adds value and there is no filler or redundancy.

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?

Given the read-only annotations, complete parameter schema, and output schema, the description supplies the core semantics needed for invocation. The only notable gap is the absence of explicit guidance on when to use this tool instead of related sibling tools.

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?

Both parameters are fully described in the schema as exact names or slugs, so schema coverage is 100%. The description does not add parameter-specific semantics, which matches the baseline expectation when the schema carries the full burden.

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: it checks whether each wallet's computed token balances match its latest synchronized snapshot. It clearly distinguishes this from siblings like get_portfolio or get_sync_status by focusing on balance reconciliation and per-wallet match status.

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

Usage Guidelines3/5

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

The description implies usage for verifying balance consistency, but it does not explicitly say when to choose this tool over related siblings such as get_portfolio_issue_summary or get_sync_status. No exclusion criteria or alternatives are mentioned.

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?