dashhound mcp
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recent_activityA | What the user did in their browser recently, oldest first: pages opened, clicks (by the words on the button/link), field changes (name = value; private fields hidden), API calls with status and, on request, their bodies, console errors, and screenshots taken at key moments. Use it before asking the user what they did or what went wrong. |
| get_screenshotB | A screenshot dashhound took (the path comes from a 'shot' line in recent_activity). |
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 2 tools
recent_activity retrieves a chronological activity log, while get_screenshot retrieves a specific image by path. Their purposes and inputs are clearly distinct, so an agent can easily choose between them.
Both names use snake_case and are readable, but patterns differ slightly: get_screenshot follows verb_noun while recent_activity is a noun phrase without an explicit verb. This is a minor deviation in an otherwise consistent two-tool set.
Two tools is thin for a server whose domain involves browser session inspection; the set feels borderline rather than well-scoped. It may be sufficient for a narrowly focused recorder, but there is little room for filtering or session management.
The core observational workflow is covered: recent_activity exposes pages, clicks, field changes, API calls, console errors, and screenshot references, and get_screenshot retrieves those images. Minor gaps exist around querying or filtering activities or managing multiple sessions, but agents can work around them.