Tokenbooks - crypto and fiat accounting and payments

Get Server Info

get_server_info

Read-onlyIdempotent

Learn what this accounting server covers before connecting: supported blockchains and fiat sources, accounting standards, plans with their capacity limits and what each tier adds, how to sign up, connection endpoint and authentication methods, and what it deliberately leaves out. Needs no credentials, so call it first when evaluating a connection, answering what Tokenbooks costs or includes, or debugging a connection.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`notes`	Yes
`title`	Yes
`pricing`	Yes
`summary`	Yes
`coverage`	Yes
`endpoint`	Yes
`limitations`	Yes
`authentication`	Yes
`gettingStarted`	Yes
`documentationUrl`	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": {
+    "authentication": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "coverage": {
+      "additionalProperties": false,
+      "properties": {
+        "accountingFrameworks": {
+          "type": "string"
+        },
+        "blockchains": {
+          "type": "string"
+        },
+        "fiat": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "blockchains",
+        "fiat",
+        "accountingFrameworks"
+      ],
+      "type": "object"
+    },
+    "documentationUrl": {
+      "type": "string"
+    },
+    "endpoint": {
+      "type": "string"
+    },
+    "gettingStarted": {
+      "additionalProperties": false,
+      "properties": {
+        "accessRequirement": {
+          "type": "string"
+        },
+        "signUpUrl": {
+          "type": "string"
+        },
+        "steps": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "accessRequirement",
+        "signUpUrl",
+        "steps"
+      ],
+      "type": "object"
+    },
+    "limitations": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "name": {
+      "type": "string"
+    },
+    "notes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "pricing": {
+      "additionalProperties": false,
+      "properties": {
+        "note": {
+          "type": "string"
+        },
+        "plans": {
+          "items": {
+            "oneOf": [
+              {
+                "additionalProperties": false,
+                "properties": {
+                  "capacity": {
+                    "const": "negotiated",
+                    "type": "string"
+                  },
+                  "name": {
+                    "type": "string"
+                  },
+                  "unlocks": {
+                    "items": {
+                      "type": "string"
+                    },
+                    "type": "array"
+                  }
+                },
+                "required": [
+                  "name",
+                  "capacity",
+                  "unlocks"
+                ],
+                "type": "object"
+              },
+              {
+                "additionalProperties": false,
+                "properties": {
+                  "capacity": {
+                    "const": "published",
+                    "type": "string"
+                  },
+                  "limits": {
+                    "additionalProperties": false,
+                    "properties": {
+                      "portfolios": {
+                        "type": "number"
+                      },
+                      "transactions": {
+                        "type": "number"
+                      },
+                      "wallets": {
+                        "type": "number"
+                      }
+                    },
+                    "required": [
+                      "portfolios",
+                      "wallets",
+                      "transactions"
+                    ],
+                    "type": "object"
+                  },
+                  "name": {
+                    "type": "string"
+                  },
+                  "unlocks": {
+                    "items": {
+                      "type": "string"
+                    },
+                    "type": "array"
+                  }
+                },
+                "required": [
+                  "name",
+                  "capacity",
+                  "limits",
+                  "unlocks"
+                ],
+                "type": "object"
+              }
+            ]
+          },
+          "type": "array"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "url",
+        "note",
+        "plans"
+      ],
+      "type": "object"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "title",
+    "summary",
+    "endpoint",
+    "documentationUrl",
+    "authentication",
+    "notes",
+    "gettingStarted",
+    "coverage",
+    "pricing",
+    "limitations"
+  ],
+  "type": "object"
+}

First observedSep 14, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds behavioral context beyond that: it requires no credentials, which is a practical access trait, and it states the tool 'deliberately leaves out' certain content, setting expectations about scope. This is valuable disclosure without contradicting annotations.

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 two sentences, front-loaded with the purpose and a compact list of what the tool covers. The second sentence adds usage guidance and a note about credentials. Every word earns its place; it is concise yet information-dense.

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?

Given the tool has no parameters and an output schema is present (so return format is presumably documented), the description covers everything an agent needs: the scope of information, the fact that no credentials are required, and clear invocation scenarios. It even mentions exclusions, making it a complete overview tool.

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?

The tool has zero parameters, so schema coverage is trivially 100% and there is nothing for the description to explain about inputs. Per the rubric, a baseline of 4 applies for zero-parameter tools. The description does not need to add parameter semantics, and it doesn't.

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 clear purpose: to learn what the accounting server covers before connecting. It enumerates specific content areas (blockchains, fiat sources, accounting standards, plans, sign-up, endpoint, auth methods, and exclusions) and explicitly frames it as a first-step discovery tool. This clearly distinguishes it from siblings like list_chains or get_accounting_reference, which are more targeted.

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

Usage Guidelines5/5

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

The description gives explicit usage guidance: 'call it first when evaluating a connection, answering what Tokenbooks costs or includes, or debugging a connection.' It also notes that no credentials are needed, implying it is a safe, low-friction starting point. It does not explicitly name alternatives, but the role as a preliminary overview is unambiguous.

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?