Skip to main content
Glama

List reconciliation links

well_list_reconciliation_links
Read-only

List the reconciliation links of the workspace, newest first. A reconciliation link says that two records belong together: an invoice and the transaction that paid it, a receipt and its card payment, or two rows that are one company. Each row names both sides (type and id), the relationship, how the link came to exist (action), its status (active when confirmed, pending_review when it waits for a person, rejected), the confidence, the reasoning and the review task that decides it, if any.

Use it to answer "what is this invoice matched to?", "which matches wait for my review?" or "why are these two linked?". Pass entity_type and entity_id together to read the links of one record. To confirm or reject a match that waits for review, call well_resolve_reconciliation_task with its review_task_id. Page with cursor from the previous result's next_cursor.

When the token authorizes one workspace, call this directly — no workspace 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
NameRequiredDescriptionDefault
limitNoRows to return, at most 50. Default 20.
cursorNoThe next_cursor of the previous page.
statusNoOnly the links in this status: `active` (confirmed), `pending_review` (waits for a person) or `rejected`.
entity_idNoWith entity_type: the public id of the record.
entity_typeNoWith entity_id: only the links that touch this record, on either side. E.g. `invoice`, `transaction`, `company`.
workspace_idNoTarget 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_idNoThe 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.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNo
linksNo
successYes
next_cursorNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere 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.

  1. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources