Well

Re-trigger posting

well_repost_journals

Idempotent

Re-run (repost) the posting for this fiscal period's ready rows — the workspace's re-triggerable posting gap. This is the ACTION that books the rows well_list_unposted_journals lists as ready to post: when the accounting is ready and simply has not posted, calling this re-runs the deterministic posters and clears it. It operates on the ALREADY-RESOLVED workspace and takes no arguments — do not list or switch workspaces first.

This is NOT well_list_workspaces (which only enumerates workspaces and posts nothing), and NOT well_set_transaction_ledger_account (which assigns an account to ONE row that is MISSING one). This tool posts rows that already have everything they need; it never assigns an account or picks a category.

Do NOT call this while in_flight_processing is true — Well is still processing the rows (enrichment in flight); wait and re-read instead. Do NOT call it to fix a row that needs a category, a ledger account, or a party decision — those are substantive halts a retry only re-fails, and well_list_unposted_journals never lists them.

The re-run is workspace-scoped and idempotent: it re-posts the whole re-triggerable set, and the posters skip anything already booked, so a repeated press is safe. It returns enqueued (rows that reached their poster) and skipped (each row that did not, with a reason).

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
`workspace_id`	No	Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say 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.
`idempotency_key`	No	Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`skipped`	Yes
`success`	Yes
`enqueued`	Yes
`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.
`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.7/5.0

Behavior5/5

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

Beyond annotations (idempotentHint=true, readOnlyHint=false, destructiveHint=false), it reveals behavior: posts the whole re-triggerable set, skips already-booked rows, is safe to re-press, returns enqueued/skipped with reasons, and must not run while in_flight_processing is true. The single 'this read' phrase is loose, but the surrounding ACTION/write language matches readOnlyHint=false, so no contradiction.

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 definition is long but every paragraph earns its place: core action first, exclusions, safety condition, idempotency, return shape, and workspace authorization. It is front-loaded and highly scannable.

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?

With an output schema present, it still supplies operational context: when to wait, what happens to already-booked rows, which sibling to use instead, and how workspace auth affects required arguments. Nothing needed to call it correctly is missing.

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 each parameter already has a rich description, so the description's main contribution is contextualizing workspace_id (omit for single-workspace tokens, pass when several). That restates schema guidance rather than adding new parameter-level semantics.

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?

First sentence states a specific action and resource: 'Re-run (repost) the posting for this fiscal period's ready rows.' It goes beyond the title to define the exact gap and explicitly differentiates from siblings like well_list_workspaces and well_set_transaction_ledger_account, so an agent can select it without opening schemas.

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?

The description gives explicit when-to-use ('when the accounting is ready and simply has not posted') and hard when-not-to-use conditions (in_flight_processing true; rows needing a category, ledger account, or party decision), and names the alternative tools. It also covers workspace authorization, which determines whether workspace_id is required.

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?