instruckt-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_pendingA | Get all pending (unresolved) annotations from the UI. Returns annotation metadata including comment, element, page URL, and severity. Does not include screenshot data — use get_screenshot for that. |
| get_screenshotA | Get the screenshot image for a specific annotation by ID. |
| resolveA | Mark an annotation as resolved. This removes the marker from the browser on next page load. |
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 3 tools
Each tool has a clearly distinct purpose: listing pending annotations, fetching a screenshot by ID, and resolving an annotation. There is no overlap or ambiguity between them.
Names are mostly consistent with verb_noun pattern: get_all_pending, get_screenshot, but resolve is a bare verb lacking an object. Minor deviation does not hurt readability.
Three tools is a compact set for a narrow domain (annotation review and resolution). It feels slightly thin, but each tool is necessary and the scope is well-defined.
The set covers the core workflow of listing pending annotations, viewing details (screenshot), and resolving them. A minor gap is lack of access to resolved annotations, but it's not essential for the intended use.