Identified built-in tools.
UnderstandChecked MCP tools availability.
UnderstandCompiled and presented full tool inventory.
VerifyI'll list the built-in tools and check which MCP tools are available right now.
Let me pull a fuller picture of the MCP tools across servers.
Here’s the full tool inventory available in this session.
tasks (connected — 6 tools)traces and vercelStill connecting (or not yet exposing tools). Their tools will show up via search_tool once ready.
Not tools themselves, but instruction packs I can load for specialized work — e.g. pptx, docx, xlsx, review, design, shadcn, Vercel/Next.js skills, check-work, imagine, etc.
Summary: ~35 built-in tools + 6 MCP tools from tasks. Want a deep dive on any category (e.g. media, agents, scheduling)?
I'll run a reversible end-to-end demo: use a temp sandbox, exercise each tool category, then clean up everything we create.
Cleaning up created tasks and finishing the remaining demos.
Sandbox: /tmp/grok-tool-demo.nhtuB3 (created → exercised → fully removed).
Media lives under this session folder (not in your home/project tree):
images/1.jpg, images/2.jpgvideos/1.mp4, videos/2.mp4No scheduled tasks, no MCP demo task, no /tmp sandbox. Safe leftover only if you want to inspect the generated media.
Bottom line: Most tools exercised end-to-end with create→use→undo where applicable. Two MCP task APIs (pause, get_results) hit ownership/team errors; Vercel MCP needs auth.
Monitor demo also finished cleanly (monitor-event-1..3 → monitor-complete, exit 0). That closes the last background piece from the reversible tool test — nothing else left running.