Add your own check to the agent map
add_checkPuts a person in front of any step of an app's agent map, including steps the map didn't flag. It goes live at once (tasks the agent sends with its category follow it) and stays when the app is mapped again. Call get_agent_map first to see the step ids. Ask the user before adding one.
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": {
"at": "<at>",
"title": "<title>",
"question": "<question>",
"options": "<options>"
},
"name": "add_check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| at | Yes | The id of the step (node) the check sits at | |
| app | No | The app id. Default: PLURES_APP, then the default app | |
| why | No | One sentence on what goes wrong without a person | |
| show | No | The fields of the agent's data people see | |
| route | No | verifiers (default) or team, for the developer's own people | |
| title | Yes | A short name, like Check emails to customers. The category is made from it | |
| options | Yes | 2 to 8 answers, the one that lets the agent go ahead first | |
| question | Yes | What people decide, answerable from what they're shown |