Back to Prompt Library
planning
Define MCP Tool for Exam Log Access
Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.
Linked challenge: AI-Powered Exam Proctoring: MCP-Enabled Cheat Detection with Gemini 2.5 Pro and DSPy
Format
Text-first
Lines
1
Sections
1
Linked challenge
AI-Powered Exam Proctoring: MCP-Enabled Cheat Detection with Gemini 2.5 Pro and DSPy
Prompt source
Original prompt text with formatting preserved for inspection.
1 lines
1 sections
No variables
0 checklist items
Draft the conceptual MCP tool definition (YAML/JSON) for securely accessing a mock exam platform's student interaction logs. This tool should allow agents to query actions like 'time spent on question', 'external tab switches', and 'text paste events', ensuring data privacy and access control considerations.
Adaptation plan
Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.
Keep stable
Preserve the role framing, objective, and reporting structure so comparison runs stay coherent.
Tune next
Swap in your own domain constraints, anomaly thresholds, and examples before you branch variants.
Verify after
Check whether the prompt asks for the right evidence, confidence signal, and escalation path.