Tokenbooks - crypto and fiat accounting and payments

Create Workspace

create_workspace

Create a workspace when list_workspaces is empty or the user wants another; then create_portfolio. On failure, check list_workspaces before retrying.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_workspace"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Workspace name
`workspaceIntent`	No	Personal or business use	PERSONAL_EVALUATION

Output Schema

Name	Required	Description	Default
`name`	Yes
`slug`	Yes
`limits`	Yes
`planName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already declare the safety profile, including non-read-only, open-world, non-idempotent, and non-destructive behavior. The description adds useful workflow context about the next create_portfolio step and retry behavior, though it does not discuss permissions or duplicate-avoidance beyond the retry check.

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 short sentences with no wasted wording. It front-loads the creation condition and then gives the follow-up and retry guidance.

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?

For a simple two-parameter creation tool with an output schema and complete parameter descriptions, this is sufficient. It covers when to call it, what to do next, and how to recover from failure.

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 coverage is 100%, so the schema fully documents both parameters, including the workspaceIntent enum. The description does not add parameter-specific meaning, which is acceptable given the complete schema.

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: 'Create a workspace'. It also distinguishes when to use it by naming list_workspaces and the follow-up create_portfolio action.

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?

It gives explicit usage conditions: when list_workspaces is empty or the user wants another workspace. It also provides a failure-handling rule: check list_workspaces before retrying.

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?