MCP | Playbook UX #2636
Description
At the moment, running playbooks from an MCP client doesn't have a good UX due to the multiple steps involved.
- run_playbook : id
- get_playbook_status(id): completed
- get_playbook_run-steps(id): steps
- if result is in artifact, read_artifact(a_id)
if the playbook takes a while, the MCP client would need to ping multiple times, until the run is complete
Ideally, the MCP client, should run a tool and get the response in 1 step.
We could annotate playbooks as mcp: sync, in which case an MCP client would wait a little longer and get the entire result in one call.
Playbooks that are short-lived like prometheus query, sql query, can have such annotation.