Skillroute 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 |
|---|---|
| list_skillsB | Lists all available engineering skills and playbooks. |
| get_framework_skillB | Fetches specific engineering guidelines, rules, and best practices for a given framework/technology. |
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
The two tools have clearly distinct purposes: listing all available skills versus fetching details for a specific framework. There is no overlap or ambiguity an agent could encounter.
Both tool names follow a consistent verb_noun pattern (list_skills, get_framework_skill) using snake_case. The naming clearly indicates the action and target resource.
With only 2 tools, the set feels minimal but not inappropriate for a narrow domain like reference documentation. It is on the low end but earns its place.
The surface covers the basic operations for a skills reference: listing all available and retrieving one by framework. A gap might be the absence of search or filtering, but for a simple lookup tool it is largely complete.