report_outcome

When to use

Call report_outcome after using a tool that ToolCairn recommended. This is typically the final step in the discovery flow: search_tools → report_outcome. You can also report outcomes for tools found through get_stack or check_issue.

Input schema

tool_name················································································stringrequired

Name of the tool that was used (e.g. "Prisma", "Vitest", "Drizzle ORM").

outcome················································································"success" | "failure" | "partial"required

The result of using the tool. "success" for full satisfaction, "failure" for complete failure, "partial" for mixed results.

details················································································stringoptional

Additional context about the outcome — what worked, what failed, or any caveats. Helps refine future recommendations.

Examples

Reporting success

{
  "tool_name": "Prisma",
  "outcome": "success",
  "details": "Type-safe queries worked perfectly with PostgreSQL 16. Migrations ran without issues."
}

Prisma worked great for my project — type-safe queries
and migrations ran without issues on PostgreSQL 16.
// Claude will call report_outcome with:
// {
//   "tool_name": "Prisma",
//   "outcome": "success",
//   "details": "Type-safe queries worked perfectly with PostgreSQL 16..."
// }

// In Cursor chat:
// "TypeORM didn't work with my Next.js 15 + SWC setup.
//  I switched to Drizzle ORM instead."
// Cursor calls report_outcome automatically

{
  "tool_name": "TypeORM",
  "outcome": "failure",
  "details": "TypeORM decorators conflicted with SWC compilation in Next.js 15. Switched to Drizzle ORM."
}

{
  "tool_name": "Docker",
  "outcome": "partial",
  "details": "Container builds work but hot-reload does not function on Windows with volume mounts."
}

Response format

Returns a confirmation with the graph update details, including the edge weight change and new confidence score.

Success outcome response

{
  "status": "recorded",
  "tool_name": "Prisma",
  "outcome": "success",
  "graph_update": {
    "edge_weight_delta": +0.03,
    "new_confidence": 0.97,
    "affected_edges": 4
  },
  "message": "Outcome recorded. Prisma's recommendation confidence has been reinforced."
}

{
  "status": "recorded",
  "tool_name": "TypeORM",
  "outcome": "failure",
  "graph_update": {
    "edge_weight_delta": -0.05,
    "new_confidence": 0.67,
    "affected_edges": 3
  },
  "message": "Outcome recorded. TypeORM's recommendation confidence has been attenuated for this context."
}

Error codes

400················································································Bad Requestoptional

Invalid parameters. Ensure tool_name is non-empty and outcome is one of "success", "failure", or "partial".

404················································································Not Foundoptional

The specified tool was not found in the graph. Check the tool name spelling.

500················································································Internal Erroroptional

Graph update error. The outcome could not be recorded due to an internal failure.

Related tools

• search_tools — Start a new tool search
• check_issue — Diagnose issues before reporting a failure
• Feedback Loop — Learn how outcomes affect the recommendation graph