Tokenbooks - crypto and fiat accounting and payments

Get Portfolio

get_portfolio

Read-onlyIdempotent

Read one portfolio's settings and accounting policy by exact name or slug, including its financial reporting framework and legal entity type. If legalEntityType is omitted, it is unset.

Input Schema

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

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

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

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"
+]

First observedSep 14, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the fact that the tool surfaces settings, accounting policy, and a legalEntityType that may be unset, which is mild useful context but no permissions, caching, or freshness behavior.

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, zero filler, with the identifier requirement (exact name or slug) front-loaded ahead of the secondary field note. 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 the description need not explain return values, and it correctly covers the read scope and identifier form. The only gap is the absence of explicit sibling routing (get vs list), which is minor for a two-parameter read tool.

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% and both parameters already document 'exact name or slug' in their own descriptions. The 'if legalEntityType is omitted, it is unset' note concerns a returned field rather than an input, so the description adds nothing beyond the schema for the two parameters. Baseline 3 applies.

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 (Read) and resource (one portfolio's settings and accounting policy), plus the fields returned (financial reporting framework, legal entity type). The singular 'one portfolio' contrasts cleanly with the sibling list_portfolios, so an agent can distinguish them without opening a schema.

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 rather than stated: 'one portfolio... by exact name or slug' signals this is the single-record lookup versus list_portfolios, but the description never explicitly says when to prefer it or that list_portfolios is the alternative for enumerating portfolios.

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?