VibeLens
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_localhost_uiA | Gives you eyes on a locally running web app. Opens the URL in a headless Chromium browser and returns (1) a screenshot of the rendered page, (2) any console errors/warnings and failed network requests, and (3) a token-optimized DOM snapshot that preserves ids and CSS/Tailwind classes. Use it to verify or debug UI work instead of guessing: layout and alignment bugs, overflow, spacing, responsive breakpoints, hydration errors and missing assets. Read the classes in the DOM snapshot before proposing a fix so you edit real selectors. Only local addresses (localhost / private network) are permitted. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possible confusion among tools.
The single tool name follows a clear verb_noun pattern (inspect_localhost_ui), consistent with itself.
A single tool for UI inspection is too few; users would expect separate tools for screenshots, console logs, and DOM snapshots.
The tool bundles multiple functions into one call, preventing selective use and lacking fine-grained operations like element querying or interaction.