kd-scout
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 |
|---|---|
| keyword_difficultyB | Estimate keyword difficulty (0-100) from SERP signal inputs: number of words, presence of brand terms, and commercial intent markers. |
| opportunity_scoreA | Blend difficulty and monthly volume into a single 0-100 opportunity score (70% inverse difficulty, 30% log volume). |
| content_briefA | Generate a structured article brief: H2 outline, word-count target, FAQ suggestions, and schema type recommendation. |
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 in the keyword research workflow: difficulty estimation, opportunity scoring, and content brief generation. There is meaningful sequential dependency, but no functional overlap that would confuse an agent.
All tool names follow the same lowercase snake_case pattern and describe their output: keyword_difficulty, opportunity_score, content_brief. The naming convention is predictable and easy to extend.
Three tools is perfectly scoped for this server's narrow purpose. Each tool fills a distinct step in the pipeline without redundancy or unnecessary bloat.
The set covers the core lifecycle from raw signals through difficulty and opportunity scoring to a content brief, leaving no obvious workflow dead end. It lacks built-in SERP or volume retrieval, but those appear to be external inputs rather than gaps in the server's stated scope.