Clous MCP Use
Prefer MCP when the host has connected Clous remote servers because MCP preserves tool schemas and host auth UX.
Workflow
- Confirm available Clous MCP server:
clous-platform,clous-hr, orclous-employee. - List tools/resources before calling a tool.
- Use the narrowest tool that answers the request.
- For mutations, ask for confirmation when the host has no product confirmation path.
- Keep returned structured content separate from user-facing summaries.
MCP Safety Contract
- Inspect tool schemas, scopes, and exposed resources before wiring host prompts or agent actions.
- Keep server name, tool name, resource id, and caller context visible in integration notes when available.
- Prefer least-privilege tools and do not pass raw employee data to unrelated tools.
- For HR, compensation, performance, or employment-status context, include source/resource references and unresolved gaps instead of presenting retrieved context as unsupported fact.