Tokenbooks - crypto and fiat accounting and payments

List Journal Line Assignment Options

list_journal_line_assignment_options

Read-onlyIdempotent

Find the ledger accounts, saved counterparties, or responsibility centers (departments, projects, or other reporting groups) that can be assigned to an accounting entry line. Pass type to choose the lookup: ledger_account returns each account's accountNumber, counterparty returns the counterparty name, and responsibility_center returns its type key and center name.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number, starting at 1 Only for type counterparty.
`type`	Yes	ledger_account: Ledger accounts assignable to a journal line. counterparty: Saved vendors, people, or organizations assignable to a journal line. responsibility_center: Departments, projects, or other reporting groups (responsibility centers) assignable to a journal line.
`limit`	No	Maximum items to return, maximum 100. Preferred MCP pagination field. Only for type counterparty.
`search`	No	Filter by name (also matches account number for ledger accounts)
`pageSize`	No	Deprecated alias for limit, maximum 100. Prefer limit for new MCP calls. Only for type counterparty.
`portfolioRef`	Yes	Portfolio name or slug inside that workspace. Call list_portfolios to resolve it.
`workspaceRef`	Yes	Workspace name or slug. Call list_workspaces to resolve it.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`type`	Yes
`total`	No
`hasMore`	No
`accounts`	No
`counterparties`	No
`responsibilityCenters`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 24, 2026

removedInput schema / oneOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "portfolioRef": {
-        "$ref": "#/properties/portfolioRef"
-      },
-      "search": {
-        "$ref": "#/properties/search"
-      },
-      "type": {
-        "description": "Ledger accounts assignable to a journal line.",
-        "enum": [
-          "ledger_account"
-        ],
-        "type": "string"
-      },
-      "workspaceRef": {
-        "$ref": "#/properties/workspaceRef"
-      }
-    },
-    "required": [
-      "workspaceRef",
-      "portfolioRef",
-      "type"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "limit": {
-        "$ref": "#/properties/limit"
-      },
-      "page": {
-        "$ref": "#/properties/page"
-      },
-      "pageSize": {
-        "$ref": "#/properties/pageSize"
-      },
-      "portfolioRef": {
-        "$ref": "#/properties/portfolioRef"
-      },
-      "search": {
-        "$ref": "#/properties/search"
-      },
-      "type": {
-        "description": "Saved vendors, people, or organizations assignable to a journal line.",
-        "enum": [
-          "counterparty"
-        ],
-        "type": "string"
-      },
-      "workspaceRef": {
-        "$ref": "#/properties/workspaceRef"
-      }
-    },
-    "required": [
-      "workspaceRef",
-      "portfolioRef",
-      "type"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "portfolioRef": {
-        "$ref": "#/properties/portfolioRef"
-      },
-      "search": {
-        "$ref": "#/properties/search"
-      },
-      "type": {
-        "description": "Departments, projects, or other reporting groups (responsibility centers) assignable to a journal line.",
-        "enum": [
-          "responsibility_center"
-        ],
-        "type": "string"
-      },
-      "workspaceRef": {
-        "$ref": "#/properties/workspaceRef"
-      }
-    },
-    "required": [
-      "workspaceRef",
-      "portfolioRef",
-      "type"
-    ],
-    "type": "object"
-  }
-]

changedInput schema / properties / limit / description

Previous value: -"Maximum items to return, maximum 100. Preferred MCP pagination field."New value: +"Maximum items to return, maximum 100. Preferred MCP pagination field. Only for type counterparty."

changedInput schema / properties / page / description

Previous value: -"Page number, starting at 1"New value: +"Page number, starting at 1 Only for type counterparty."

changedInput schema / properties / pageSize / description

Previous value: -"Deprecated alias for limit, maximum 100. Prefer limit for new MCP calls."New value: +"Deprecated alias for limit, maximum 100. Prefer limit for new MCP calls. Only for type counterparty."

changedInput schema / properties / type / description

Previous value: -"Ledger accounts assignable to a journal line."New value: +"ledger_account: Ledger accounts assignable to a journal line. counterparty: Saved vendors, people, or organizations assignable to a journal line. responsibility_center: Departments, projects, or other reporting groups (responsibility centers) assignable to a journal line."

AddedSep 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral detail beyond the schema by specifying what each type returns: accountNumber for ledger_account, counterparty name, and type key plus center name for responsibility_center. This gives the agent a concrete expectation of the result shape.

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 tight sentences: the first states the tool's purpose and scope, and the second explains the type-driven behavior. There is no filler, and the most important usage signal (`Pass type`) is front-loaded.

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 read-only lookup tool with seven fully documented parameters, rich annotations, and an output schema, the description covers everything an agent needs to select and invoke it correctly. Pagination, deprecation, and validation details are already in the schema, so the description does not need to repeat them.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by mapping each `type` enum value to its corresponding return fields, which is not stated in the parameter descriptions. It does not repeat pagination details, but those are already fully documented in the 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 opens with a specific verb ('Find') and a concrete resource: ledger accounts, saved counterparties, or responsibility centers assignable to an accounting entry line. It also distinguishes the three lookup modes by name, so an agent can tell exactly what this tool returns without opening the schema.

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

Usage Guidelines4/5

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

It clearly instructs the agent to pass `type` to choose the lookup, which covers the core usage decision. No sibling tool appears to overlap with this function, so the absence of explicit when-not-to-use guidance is acceptable; the context is clear even though exclusions are not spelled out.

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?