render-mcp

Each tool targets a clearly distinct concern: accessibility violations, computed layout, console/network errors, post-JS HTML, screenshots, and PDF output. There is no realistic overlap where an agent would be unsure which tool to call.

All names are lowercase snake_case and readable, but the pattern is mixed: inspect_element and screenshot_url are imperative, while accessibility_audit, page_diagnostics, rendered_html, and url_to_pdf are noun-like or descriptive phrases. A uniform verb_noun style would make the set more predictable.

Six tools is a well-scoped count for a render/inspection server. Each tool covers a meaningful, non-redundant capability without bloating the surface.

The set covers the core rendered-page workflows: getting content, seeing it, printing it, auditing accessibility, inspecting layout, and diagnosing errors. A minor gap is the lack of interaction or script execution tools, but for the stated rendering/diagnostics purpose the coverage is strong.