Well

List ledger accounts

well_list_ledger_accounts

Read-only

List the workspace's chart of accounts (COA) — every ledger account a counterparty default or a transaction can be assigned to. Use it to name a real ledger_account_id in a write instead of guessing one.

Each account carries id (the ledger_account_id the writes take), name, and code (its account number, e.g. "401" for a vendor or "411" for a customer under the FR PCG) where the account has one.

truncated: true means the chart holds MORE accounts than this page carries; read the rest with well_query_records on the ledger_accounts root.

success: false means the chart could not be read, NOT that the workspace has none. An empty accounts on a failed read is unknown, never "no chart of accounts".

When the token authorizes one workspace, call this directly — no other tool call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max accounts to return; the chart is capped either way.
`workspace_id`	No	Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose which.
`conversation_id`	No	The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`success`	Yes
`accounts`	Yes
`returned`	No
`truncated`	No
`conversation_id`	No	The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
`resolved_workspace`	No	The workspace that answered, when the caller named none and the token authorizes several.
`conversation_id_note`	No	Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.
`conversation_id_source`	No	Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 22, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description goes well beyond the readOnlyHint, openWorldHint, and destructiveHint annotations. It explains the error semantics: 'success: false means the chart could not be read, NOT that the workspace has none', the meaning of truncated: true and how to fetch more, and the workspace selection behavior (will not guess). These are important behavioral disclosures not encoded in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but well-structured, front-loading the core purpose before covering fields, pagination, error semantics, and usage. Every section adds value; some redundancy exists (e.g., repeated workspace guidance), but it remains focused and readable. A solid 4.

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?

Given the output schema exists (so return values need not be explained), the description covers the critical operational context: pagination via truncation, error semantics, workspace selection, and mapping to real ledger_account_ids. Nothing an agent requires to call this tool correctly is missing.

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 non-trivial context for workspace_id, explaining when it is required and that the read will not guess which workspace to use. It also subtly reinforces the limit param ('the chart is capped either way'). This extra guidance justifies a 4.

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 clearly states the tool lists the workspace's chart of accounts, and explains its purpose: to obtain a real ledger_account_id for writes. It differentiates from siblings by referencing well_query_records for pagination and by focusing on the COA listing role, while mentioning what the accounts carry (id, name, code). This is a specific verb+resource with clear scope.

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?

Explicitly states when to call directly (when the token authorizes one workspace) and when to pass workspace_id (when it authorizes several). It also clarifies the relationship to well_query_records for reading additional pages of the chart. This gives clear when-to-use guidance and distinguishes from alternatives.

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

All Well 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?