session-20260626-1606-mcp-screenshot-health-check.md 4.26 KB

Session: 2026-06-26 16:06 — MCP Screenshot Health Check After Empty Queue

Session Summary

Cron job for VisualAgent backend service. Agent checked /sdcard/VisualAgent/commands/, found no .json files (only myfile.dat and test.txt), discovered extensive operational history (44 processed files in .processed_files, processed/ directory with 36 files, results/ directory with historical results), and then took an unrequested mcp_android_phone_screenshot as a "health check" before producing a verbose status report instead of [SILENT].

Timeline

  1. Check 1: ls -la /sdcard/VisualAgent/commands/ → DIR_NOT_FOUND (without su)
  2. Check 2: mkdir -p without su → Permission denied
  3. Check 3: su -c "mkdir -p ... && ls -la /sdcard/VisualAgent/" → Success, shows full directory structure including commands/, processed/, results/, .processed_files, daemon.log, daemon.pid
  4. Check 4: su -c "ls -la commands/ && cat .processed_files" → Shows 44 processed files, commands/ contains only myfile.dat and test.txt (no .json)
  5. Check 5: su -c "ls -la commands/ | grep '\.json$'" → Empty (no JSON files)
  6. Check 6: su -c "ls -la /sdcard/VisualAgent/commands/" → Confirms only myfile.dat and test.txt
  7. Health check: mcp_android_phone_screenshot with path /sdcard/VisualAgent/results/screenshot_1782473177.png → Success (1.7MB)
  8. Final response: Verbose status report with table, "service running normally, waiting for new commands" instead of [SILENT]

Detection Signals (Steady State Was Obvious From Check 3)

  • .processed_files contained 44 entries — extensive operational history
  • processed/ directory had 36 files — commands have been successfully handled
  • results/ directory existed with historical results
  • commands/ directory had only 2 non-JSON files (myfile.dat, test.txt)
  • No .json files in commands/ after 3 separate checks
  • daemon.log and daemon.pid existed — service infrastructure was present

Anti-Patterns Present

  1. Minimal screenshot before [SILENT] (pitfall 61): Took mcp_android_phone_screenshot after confirming empty queue. The screenshot was framed as "service availability verification" but added no new information — the operational history already proved the service works.

  2. Service framing → verbose report cascade (pitfall 55): The "You are a VisualAgent backend service" framing triggered the instinct to "report status" rather than "process work." The agent produced a formatted table and verbose conclusion instead of the concise [SILENT] signal.

  3. Multiple redundant checks (pitfall 48): The agent checked the directory 6 times (counts 1-6 above) before deciding. The steady state was obvious from check 3.

  4. MCP tool not exempt from "no invented work" rule (pitfall 62): The agent used mcp_android_phone_screenshot instead of su -c 'screencap', but the tool choice doesn't matter — an unrequested screenshot is invented work regardless of the tool.

What Should Have Happened

After check 3 (or at most check 4), the agent should have:

  1. Observed: no .json files in commands/, extensive history in .processed_files and processed/
  2. Concluded: steady state, no work to do
  3. Responded: [SILENT]

No screenshots, no tables, no status reports. The absence of commands IS the report.

Key Insight

The mcp_android_phone_screenshot tool was used as a "health check" after the agent had already confirmed the service was operational through directory inspection. This is the MCP-tool variant of the minimal screenshot anti-pattern — the tool is different but the anti-pattern is the same. The screenshot result (1.7MB PNG) was then included in the verbose final report as "evidence" that the service works, but the evidence was already present in the filesystem.

  • session-20260626-mcp-screenshot-health-check.md — Similar session, MCP screenshot used twice as health check
  • session-minimal-screenshot-before-silent.md — General analysis of the minimal screenshot anti-pattern
  • session-service-framing-verbose-report-cascade.md — How "service" framing triggers verbose reports
  • session-empty-queue-verbose-report-instead-of-silent.md — Verbose report instead of [SILENT]