Single Agent – With Tools
Tool integration via agent_role field. Validates protocol semantics for tool-enabled workflows.
Website Source Model
Actual page source: Website aggregate projection layer in MPLP_website/lib/content/flows.ts.
Upstream provenance: IDs, titles, and boundary classification come from tests/golden/flows/registry.ts; per-flow scenario detail is summarized from the upstream asset tests/golden/flows/flow-03-single-agent-with-tools/README.md. The Docs page is a secondary reference at verified flow reference.
Goal
Validate that the runtime can handle tool-based steps with proper agent_role semantics.
Success Criteria
Tool steps execute via agent_role, outputs captured in trace.
Sequence
Execution Steps
Website summary of the scenario sequence represented by this flow.
Tool Context
Context for API testing workflow.
Tool Steps
Steps with agent_role: curl_executor, jq_processor.
Role-Based Execution
Each role handles specific tool type.
Result Capture
Tool outputs recorded in trace.
Tool Context
Context for API testing workflow.
Tool Steps
Steps with agent_role: curl_executor, jq_processor.
Role-Based Execution
Each role handles specific tool type.
Result Capture
Tool outputs recorded in trace.
Core Boundary
Core Flow Scope
This core flow aggregates the published boundary expectations from the following MPLP modules.
Plan Module
Steps with tool roles MUST use agent_role field (not fictional tool_name).
Extension Module
Tool invocations MUST go through protocol-defined extension points.
Trace Module
Tool execution results MUST be captured in trace events.
Validation
Failure Conditions
Execution of this core flow should be treated as outside the published boundary expectations if any of the following conditions occur.
Tool invocations bypass the agent_role mechanism.
Tool outputs are not captured in trace.
Security sandbox violations during tool execution.
Non-deterministic tool behavior in golden tests.
Core Published Boundary
FLOW-01~05 form the published v1.0 core boundary. Implementations are expected to satisfy this flow without violating the upstream constraints summarized above.
Failure to satisfy this core flow indicates that the published core-boundary expectations were not met.