demandscope
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEMANDSCOPE_CACHE_DIR | No | Directory for the file-based TTL cache. | .cache/demandscope |
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 |
|---|---|
| github_repo_signalA | GitHub repo count and top-star sums for a search query (developer interest / competition proxy). |
| github_trendC | GitHub repos created in the last N days vs the prior window; growth_ratio > 1 means accelerating supply/interest. |
| hn_signalA | Hacker News story count for a query over the last N days (tech-audience attention proxy). |
| hn_trendB | Hacker News story count for the last N days vs the prior window; growth_ratio > 1 means accelerating attention. |
| npm_downloadsB | Last-month downloads for an npm package (comparable-product demand). |
| pypi_downloadsA | Last-month downloads for a PyPI package (comparable-product demand). |
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 6 tools
Each tool targets a distinct source (GitHub, Hacker News, npm, PyPI) and a distinct metric (absolute signal vs trend vs downloads). Even the GitHub and HN pairs are clearly separated by the signal/trend distinction, leaving no meaningful overlap.
Most tools follow a source_metric pattern: github_repo_signal, github_trend, hn_signal, hn_trend, npm_downloads, pypi_downloads. The only minor inconsistency is that npm and PyPI use 'downloads' while GitHub and HN use 'signal'/'trend', but the pattern remains predictable and readable.
Six tools is well-scoped for a demand-signal aggregator covering multiple external data sources. Each tool earns its place by representing a distinct signal-source combination, and the count feels neither too thin nor bloated.
The toolset covers both absolute and trend signals for GitHub and Hacker News, plus package downloads for npm and PyPI. A minor gap is the lack of trend/growth comparison for npm and PyPI downloads, but the core demand-signal surface is otherwise well covered.