signal-scanner
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_CHAT_ID | No | Telegram chat ID from @userinfobot (optional, required for Telegram notifications) | |
| TELEGRAM_BOT_TOKEN | No | Telegram bot token from @BotFather (optional, enables Telegram notifications) |
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 |
|---|---|
| scanA | Screen symbols against the ruleset and return which rules fired per symbol. Examples: - "Run my scanner" -> symbols=[] - "Scan AAPL, MSFT and NVDA" -> symbols=['AAPL','MSFT','NVDA'] - "Any signals on bitcoin?" -> symbols=['BTC-USD'] |
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
There is only one tool, so there is no possibility of misselection or overlap with another operation. An agent cannot confuse 'scan' with anything else on this server.
With a single tool there is no internal inconsistency to violate, which is inherently predictable. However, 'scan' is a bare verb with no noun component, so it doesn't model the conventional verb_noun pattern.
One monolithic tool carries the entire server's surface, which is too thin for a domain that implies ruleset management and result inspection. Everything must funnel through a single overloaded entry point.
Scanning symbols is covered, but there is no way to list, create, edit, or validate the ruleset the scanner runs against, nor to retrieve or persist prior results. The core action exists, but the lifecycle around it is a dead end.