A support desk an agent can operate
Looking for a WebMCP client…
This page registers four WebMCP tools — search_tickets, create_ticket, close_ticket and escalate_ticket, plus get_tool_usage, which lets an agent read back what agents have done here. Open this page in a browser whose agent speaks WebMCP and ask it to find a ticket and close it — or press the button below — then look at the dashboard.
Runs the five calls below through the real instrumented tools — same wrapper, same beacon, same endpoint an agent would hit. Every record it writes is tagged clientName: simulated-agent, so it can never be mistaken for an agent that actually came by.
search_tickets— finds the ticketcreate_ticket— opens a new oneclose_ticket— closes what it resolvedcreate_ticket— fails: no subjectget_tool_usage— reads its own trail
No tickets.
A WebMCP tool call never leaves the browser. There is no request, no user agent, no line in an access log. Everything else on a website is measured whether anyone decided to or not; this is the one kind of traffic that is measured only on purpose. Nothing on this page tells the tools they are being watched — one call wraps the list, and that is the whole installation.