Tokenbooks - crypto and fiat accounting and payments

List Portfolios

list_portfolios

Read-onlyIdempotent

List portfolios available in a workspace, or search by name or slug.

Input Schema

Name	Required	Description
`page`	No	Page number, starting at 1
`limit`	No	Maximum items to return, maximum 100. Preferred MCP pagination field.
`query`	No	Optional portfolio name or slug search query
`pageSize`	No	Deprecated alias for limit, maximum 100. Prefer limit for new MCP calls.
`workspaceRef`	Yes	Workspace exact name or slug

Output Schema

Name	Required	Description	Default
`data`	Yes
`pagination`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```

Changed2 schema fields changedSep 20, 2026

addedInput schema / properties / query

Added value: +{
+  "description": "Optional portfolio name or slug search query",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "createdAt": {
+            "format": "date-time",
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "updatedAt": {
+            "format": "date-time",
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "createdAt",
+          "updatedAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pagination": {
+      "additionalProperties": false,
+      "properties": {
+        "page": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "pageSize": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "totalCount": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        },
+        "totalPages": {
+          "maximum": 9007199254740991,
+          "minimum": -9007199254740991,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "page",
+        "pageSize",
+        "totalCount",
+        "totalPages"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data",
+    "pagination"
+  ],
+  "type": "object"
+}

First observedSep 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is fully covered. The description adds the search capability but says nothing about pagination defaults, result limits, or ordering, so it adds only marginal behavioral context.

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?

A single tight sentence with the primary action front-loaded and no filler. Every clause earns its place.

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?

An output schema exists, so return values need not be explained, and annotations plus full schema coverage carry the rest. Only minor gaps remain around default page size and whether results are filtered by the workspace automatically.

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%, so parameters (including the deprecated pageSize alias and query semantics) are fully documented in the schema. The description restates the name/slug search but adds no syntax or format detail beyond the schema, which is the expected baseline.

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

Purpose4/5

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

States a specific verb (list) and resource (portfolios) with workspace scope, and mentions the search-by-name/slug capability. It does not differentiate from close siblings like get_portfolio (single portfolio) or list_portfolio_transactions, but the purpose is unambiguous.

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?

Usage is implied by 'list portfolios available in a workspace' but there is no explicit guidance on when to use this versus get_portfolio or list_portfolio_transactions, and no stated prerequisites beyond the required workspaceRef.

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?