LLMScout
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| runB | Run the llmscout CLI (init/check/fleet subcommands). |
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 possibility of confusing it with others. The description clearly states the tool runs the LLMScout CLI with init/check/fleet subcommands, making its purpose distinct and unambiguous.
The single tool name 'run' is a clear verb that directly reflects its action. Since there is only one tool, naming consistency is inherently maintained with no conflicting conventions.
The server exposes only one tool, which feels thin for a typical MCP server. While the CLI covers multiple subcommands, a richer set of individual tools might better match the expected scope and provide finer-grained control.
The tool description indicates it can run all the essential CLI subcommands (init/check/fleet), so the core functionality is covered. There are no obvious gaps in the agent's ability to perform the intended operations through this single tool.