shpbl-scan-coverage-autopilot
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 |
|---|---|
| scan_analyze_coverageC | Find risk-weighted scan blind spots using explicit time |
| scan_planC | Generate a deterministic capacity-safe risk-weighted scan plan |
| scan_compareB | Compare two sealed scan plans after verifying both seals |
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 maps to a distinct stage of the scan-coverage workflow: analyzing blind spots, generating a plan, and comparing sealed plans. There is no meaningful overlap that would cause an agent to pick the wrong tool.
All tools share a clear scan_ prefix and use snake_case action-oriented names. scan_plan is slightly less explicit than the verb_noun pattern of the others, but the convention is still easy to predict.
Three tools is at the lower end of the ideal range but is well-scoped for the server's narrow autopilot purpose. Each tool earns its place and no tool feels redundant.
The set covers the core cycle of analyzing, generating, and comparing scan plans. There are minor gaps, such as no explicit plan listing or management operation, but the primary workflow is supported without dead ends.