What agents did with these tools

Looking for a WebMCP client…

Live, from this demo only. Argument values are never recorded — key names and types only — and nothing here identifies a person.

No WebMCP client in this browser?

Most browsers still have none, and an empty dashboard for that reason looks exactly like an empty dashboard because the measurement is broken. So run the tools yourself and watch the numbers below move.

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.

  1. search_tickets — finds the ticket
  2. create_ticket — opens a new one
  3. close_ticket — closes what it resolved
  4. create_ticket — fails: no subject
  5. get_tool_usage — reads its own trail

Loading…