ami_write_findings
Write the judgement sections of an agent workflow run's scorecard after retrieving its brief with ami_get_scorecard, grounding each narrative in the run's own evidence.
Instructions
Write the judgement sections of a run's scorecard. The server computes every number and the three sections that follow from them; these four are readings of the work that no arithmetic produces, so they are yours to write. Call ami_get_scorecard first and use narration_brief.sections_awaiting_you - it carries the brief for each. Ground every sentence in the run's own evidence; do not invent industry context you were not given.
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": {
"run_id": "<run_id>"
},
"name": "ami_write_findings"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| run_id | Yes | The submitted run. | |
| key_finding | No | Optional. Overrides the derived summary if you have read the output and know better than the arithmetic does. | |
| industry_next_step | No | One thing the business should decide or standardise. | |
| workflow_next_step | No | One concrete change, specific enough to act on this week. | |
| industry_opportunity | No | What this workflow being agent-run means commercially. Say so plainly if you were given no industry context. | |
| workflow_opportunity | No | The single biggest improvement available to this workflow. Name the stage. |