Back to Prompt Library
implementation

MCP Tool Integration Prompt

Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.

Linked challenge: Cybersecurity M&A Due Diligence

Format
Text-first
Lines
1
Sections
1
Linked challenge
Cybersecurity M&A Due Diligence

Prompt source

Original prompt text with formatting preserved for inspection.

1 lines
1 sections
No variables
0 checklist items
For the 'Cyber Risk Analyst' agent, design MCP-enabled tool integrations to access a simulated external threat intelligence platform (API endpoint: `https://api.threatintel.com/v1/search_vulnerabilities?query=`) and an internal security audit report database (API endpoint: `https://internal.sec.db/audit_reports?company=`). Detail the expected input/output for these tools and how the agent will use them for risk assessment.

Adaptation plan

Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.

Keep stable

Hold the task contract and output shape stable so generated implementations remain comparable.

Tune next

Update libraries, interfaces, and environment assumptions to match the stack you actually run.

Verify after

Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.