Skip to main content
Glama

Tokenbooks - crypto and fiat accounting and payments

List Journal Line Assignment Options

list_journal_line_assignment_options
Read-onlyIdempotent

Find ledger accounts, saved counterparties, or responsibility centers (departments or projects) assignable to an accounting entry line.

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": {
      "workspaceRef": "<workspaceRef>",
      "portfolioRef": "<portfolioRef>",
      "type": "<type>"
    },
    "name": "list_journal_line_assignment_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1 Only for type counterparty.
typeYesledger_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.
limitNoMaximum items to return, maximum 100. Preferred MCP pagination field. Only for type counterparty.
searchNoFilter by name (also matches account number for ledger accounts)
pageSizeNoDeprecated alias for limit, maximum 100. Prefer limit for new MCP calls. Only for type counterparty.
portfolioRefYesPortfolio name or slug inside that workspace. Call list_portfolios to resolve it.
workspaceRefYesWorkspace name or slug. Call list_workspaces to resolve it.

Output Schema

NameRequiredDescriptionDefault
typeYes
totalNo
hasMoreNo
accountsNo
counterpartiesNo
responsibilityCentersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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."
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered and the description does not contradict it. The description adds no behavioral context of its own, such as whether results are bounded, how search interacts with the type enum, or that pagination applies only to counterparty lookups (that restriction lives only in the schema).

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 sentence with the resource set and the assignment scope both front-loaded. There is no filler, repetition of the title, or trailing caveats.

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?

With an output schema present, return values need not be explained, and the description correctly focuses on what kinds of options are returned. For a read-only lookup tool of this complexity the definition is nearly sufficient; it only lacks any hint about the pagination/search asymmetry across the three types, which an agent must currently dig out of the schema.

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% and every parameter, including the type enum values and the deprecated pageSize alias, is documented in the schema itself. The description contributes no additional parameter meaning, so the baseline 3 applies.

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?

The description names a specific verb ("Find") and enumerates the exact resources returned: ledger accounts, saved counterparties, and responsibility centers. The clause "assignable to an accounting entry line" scopes the result set well. It stops short of naming a sibling to differentiate from, so it lands at 4 rather than 5.

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 only implied by the phrase "assignable to an accounting entry line" — an agent can infer this is a lookup step before composing a journal line, but nothing states when to call it versus get_filter_options, get_accounting_reference, or the rules-listing siblings. No exclusions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources