log_outcome
Resolve a prediction with the observed signal — interpretation-free record.
How to use it
log_outcome is exposed by the Openexp MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the log_outcome tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
FULL OPENEXP LISTINGOther tools in Openexp (16)
actual_signal
yes
add_memory
Store a memory. Supports clientid for entity tagging
applied_action
yes
case_id
yes
cited_step
yes
days_to_resolve
yes
expected_signal
yes
expected_window_days
yes
log_prediction
Log a pack-grounded prediction. Required when an installed experience pack cites a specific relativeday as the basis for an action recommendation.
memory_stats
Collection stats: point counts by source/type, session count
notes
optional
pack_author
yes
pack_id
yes
prediction_id
yes
prevented_action
optional
search_memory
Hybrid search: semantic similarity + BM25 + recency