MCP server for integrating with Boomi AtomSphere platform, enabling process execution, monitoring, and diagnostics
Server has 7 tools with basic descriptions and some parameter documentation, but significant gaps in schema completeness, parameter descriptions, and error handling guidance. Tool names follow verb_noun convention (good), but descriptions are inconsistent in depth. Most tools lack structured output schemas and error recovery guidance. Parameters like process_id and atom_id have descriptions, but optional parameters (process_id in diagnose_last_execution, limit in list_executions) lack clarity on defaults and constraints. No input validation rules documented. Error handling returns generic exception strings rather than actionable recovery steps.
Deep-diagnose the most recent execution of a process. Fetches all available execution data — audit log, connector records, error audit entries — and provides a root-cause analysis with fix suggestions. Use this when a user asks 'what went wrong?' or 'find the error in the last run'.
Check the status of a Boomi process execution.
List all online Atoms (runtime environments) in the account.
List recent process executions in the account.
List all available Boomi processes (pipelines) in the account.
Execute a Boomi process on a specific Atom.
Output schemas not documented. Tools return free-text strings (e.g., list_processes returns formatted text) rather than structured JSON objects. LLMs cannot parse or chain results reliably.
Error handling returns raw exception strings (e.g., 'Failed to list processes: {str(e)}') without recovery guidance. LLMs cannot determine if errors are retryable, user-fixable, or fatal.
Optional parameters lack default value documentation. list_executions(process_id='', limit=10) and diagnose_last_execution(process_id='') use empty strings as 'no filter' signals, but this is not documented in parameter descriptions.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2026-07-28+ | v2 |
Test that the MCP server can connect to Boomi successfully.
No input validation rules documented. Parameters like limit (integer) lack min/max constraints. LLMs could pass limit=999999 or negative values without guidance.
Destructive operation (run_process) lacks confirmation or dry-run pattern. No warning that this modifies state and cannot be undone. No idempotency guarantee documented.