TaskBounty Check
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_repoA | Scan a LOCAL repository for GitHub Actions + CI maintenance hygiene. Reads only workflow files on disk; makes no network requests and uploads nothing. Returns a text summary of findings by category with file/line and suggested fixes. |
| explain_findingA | Explain what a finding means and why it matters, in plain language. Pass the rule id (e.g. unpinned-action) or a category. No network, no file access. |
| generate_fix_planA | Return a step-by-step fix plan as TEXT for a given rule (and optionally a local repo path for context). It NEVER modifies files; the user applies changes explicitly. |
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: scanning produces findings, explaining interprets them, and generating a fix plan suggests steps. There is no overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (explain_finding, generate_fix_plan, scan_repo), making them predictable and easy to understand.
With only 3 tools, the set is tightly scoped to a specific workflow (scan, explain, fix). This is appropriate for a focused server, avoiding unnecessary complexity.
The tools cover the main workflow from scanning to understanding to suggesting fixes. A minor gap is the lack of a tool to list all possible rules without scanning, but the workflow remains functional.