These parameters and conventions apply to all V2 MCP tools.

Workflow Sessions

All tools accept an optional workflow_id parameter (UUID format).

{
  workflow_id: "550e8400-e29b-41d4-a716-446655440000"
}

Use it to:

• Group related calls — Tools called with the same workflow_id are linked for analytics and debugging
• Deterministic results — The same workflow_id returns consistent results across repeated calls
• Correlate feedback — Pass workflow_id to submit_feedback to link feedback to a specific session

Generate a UUID at the start of a workflow and pass it to every tool call in that session.

Export Formats

Three tools support large result exports: entity_resolve, entity_enrich, and entity_find.

The export_format parameter controls how results are returned:

Export URLs are valid for 1 hour. Use an export format for result sets larger than 100,000 records — inline responses are capped at a sample size.

// Inline sample (default)
await entity_resolve({ identifiers: [...] });

// Full export as JSONL
await entity_resolve({ identifiers: [...], export_format: "jsonl" });
// Returns: { export_url: "https://...", record_count: 1240000 }

Tracing

Every tool response includes a tool_trace_id field — a unique identifier for that specific tool invocation.

{
  "tool_trace_id": "trc_01j8x...",
  ...
}

Include this ID in support requests. It lets the Watt team look up the exact execution, inputs, and outputs for debugging.