source_write_recover
Resolve a pending or uncertain source write by checking whether it committed, without writing again.
When to use it
Use source_write_recover to recover an uncertain source write. This tool operates at workspace scope. It does not require a project context unless a filtering argument explicitly asks for one.
Plugin requirements
Iceberg connector-backed source writes. Durable source-write execution and recovery currently support @craven/iceberg endpoints. Receipt reads inspect an existing operation. Other connectors do not automatically gain this support; write policies, grants and API-key authentication still apply. Use the plugin setup guides for configuration. Inspect the workspace’s plugin installations and check the installation before executing it.
Requires API-key authentication. Recovery continues an existing source-write operation; do not replace it with a new write request.
Arguments
| Name | Type | Required | Default | Constraints |
|---|---|---|---|---|
sourceId | string | Yes | — | Format: uuid; Pattern constraint; see full schema |
operationId | string | Yes | — | Format: uuid; Pattern constraint; see full schema |
View the complete input schema, including nested contracts and alternative shapes. The schema is extracted from the workspace server’s Zod definitions. Runtime validation also enforces custom checks that JSON Schema cannot express.
Response shape
The operation-specific payload is returned in data; its contents follow the operation described above.
MCP returns a text block containing the JSON operation result and a
structuredContent copy. The envelope includes data, completeness,
truncated, freshness, and warnings. Depending on the operation it can also
include nextCursor, evidence, job, or receipt.
Check those fields before treating a conversational summary as the result.
When a job is returned, inspect its status with the appropriate execution tool;
a queued response is not confirmation that work finished. Follow evidence links
when checking the underlying records.
Input methods
This request illustrates the argument structure. Replace every angle-bracket placeholder with a real value and supply any applicable optional fields from the schema. Nested business contracts must match your actual configuration. Send it through an authenticated, initialized MCP client; this JSON alone does not establish a session or sign you in.
Use Semogram’s source_write_recover tool to recover an uncertain source write. Inspect the required inputs and target first, then show me what will change before executing it.
Use real resource IDs returned by earlier reads; a resource name is not a UUID. Do not fill missing business inputs with invented values.
Use a workspace API key with data:write. Set SEMOGRAM_API_KEY in your shell; replace resource placeholders with real IDs. This is an HTTP resource request, not an MCP JSON-RPC message.
curl --request POST "https://platform.semogram.com/api/v1/data-endpoints/<SOURCE_ID_UUID>/source-writes/<OPERATION_ID_UUID>/recover" \
--header "Authorization: Bearer ${SEMOGRAM_API_KEY}"This is an MCP tools/call request, not a form to paste into Semogram. Send it through an authenticated, initialized MCP client.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "source_write_recover",
"arguments": {
"sourceId": "<SOURCE_ID_UUID>",
"operationId": "<OPERATION_ID_UUID>"
}
}
}FAQ
What access and approvals are required?
Required permission scopes: data:write.
OAuth uses current workspace membership; API keys use their assigned scopes
and grants. Discovery can exclude tools the caller cannot use.
Read-only annotation: No. Destructive annotation: No. Follow the operation’s declared contract and any applicable server-side approval policy.
How should I handle retries?
The server marks this operation as idempotent. When an idempotencyKey is accepted, keep the same key only for a retry of the exact same input; use a new key for new work. For 429 responses, honor Retry-After rather than retrying immediately.
Why is this tool missing or returning an error?
Requires API-key authentication. Recovery continues an existing source-write operation; do not replace it with a new write request. See connection, authentication and troubleshooting for sign-in, scope, resource access, and rate-limit errors.