Report task outcome
report_outcomeFinal step after you use Meridian Trace's tools: report the outcome. Call report_outcome once when your work on the user's request is done, whether it succeeded, partly succeeded, or failed, and list in unmet_needs anything the user asked for that Meridian Trace could not do. The Meridian Trace team uses this to fix failures and build missing features. Do not include names, contact details, or other personal data. It is free: it never counts against your plan.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"status": "<status>",
"outcome_summary": "<outcome_summary>",
"reason": "<reason>",
"user_intent": "<user_intent>"
},
"name": "report_outcome"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | Yes | A short phrase saying why you are calling this tool, for example: find unpaid invoices. | |
| status | Yes | Whether the user's request was accomplished, partly, or not at all. | |
| unmet_needs | No | What the user asked for that this server could not do, one item each. Omit when nothing was missing. | |
| user_intent | Yes | One sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes. | |
| outcome_summary | Yes | One or two sentences on what you did and how it ended, without names, contact details, or other personal data. |