Prevent redundant browsing requests
The agent determines if a URL fetch has already been performed recently and can reuse the result, avoiding duplicate API calls and saving budget.
How it works
The agent prepares a browse request with a specific URL and includes its history of previous tool calls. It sends this to the Agent Preflight MCP server. The server checks if the URL matches a previous successful call within the freshness TTL. If a match is found, the server returns a 'reuse' decision with a result reference. The agent then retrieves the cached result instead of making a new HTTP request. If no match is found, the server returns 'allow', and the agent proceeds to fetch the URL via the companion browse server.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Check if I should reuse a previous result for this URL: https://example.com, with history of recent successful fetches.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
reuse recommends using your prior resultReference; matchedCallId identifies its history entry.Agent Preflight MCP documentation