Loading ToolBench
PointDev bridge server — connects the Chrome extension to AI coding tools via MCP
PointDev Bridge exposes 4 read-only tools with minimal descriptions and no input validation. Tool names follow verb_noun convention (get_*), but descriptions are terse (avg 85 chars, well below the 194-char baseline). No parameter descriptions exist for get_screenshot's 'index' parameter. Output schemas are undocumented, LLMs cannot plan downstream calls or extract structured data. All tools are READ_ONLY, reducing risk, but lack error handling guidance and recovery paths. The server is incomplete: index.ts comments indicate 'MCP stdio server will wire these handlers in a future release,' meaning tool handlers are defined but not yet integrated into the MCP protocol layer.
Retrieves all annotations (circles, arrows, freehand, rectangles) from the current session
Retrieves a specific screenshot by index, including the image data and metadata (timestamp, trigger, voice context, description parts)
Retrieves the current capture session, excluding screenshot dataUrls to reduce payload size
Retrieves the voice recording transcript and segments from the current session
No output schemas documented. LLMs cannot infer what fields to expect from get_session, get_voice_transcript, or get_annotations. This blocks downstream tool composition and forces LLMs to guess at response structure.
Parameter 'index' in get_screenshot lacks a description. LLMs cannot determine valid range, whether 0-indexed or 1-indexed, or what happens if index is out of bounds.
Tool descriptions are terse (avg 85 chars vs 194-char baseline). 'Retrieves the current capture session, excluding screenshot dataUrls to reduce payload size' lacks context on WHEN to call this vs other tools, what structure is returned, or how to use the data.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 37 | 2026-07-28+ | v2 |
No error handling or recovery guidance. If get_screenshot index is out of bounds, or if no session exists, tools return nothing. LLMs have no guidance on what to do next.
Tool handlers are defined in mcp.ts but NOT wired into the MCP protocol layer. index.ts comment states 'MCP stdio server will wire these handlers in a future release.' Tools exist in code but are not yet callable via MCP.