ASTRO
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 |
|---|---|
| astro_get_startedB | Explain public access; no signup, credentials or trial activation needed. |
| astro_signalB | Read composite, market regime, component signals and source timestamps. |
| astro_contextB | Read market context, score explanations and available prediction-market inputs. |
| astro_basketB | Read ten-asset rankings, funding, volatility, strategy assessments and freshness. |
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 4 tools
The three read-oriented tools (signal, context, basket) target different data payloads, but signal and context both concern market analysis and could be conflated by an agent seeking regime or explanation data. get_started is clearly distinct as an onboarding tool. Overall mostly distinct with minor overlap.
All tools use the astro_ prefix and snake_case, providing a predictable namespace. The only deviation is the verb phrase get_started among noun-based resource tools, but consistency remains high.
Four tools is well within the ideal range and each covers a distinct area: onboarding, signals, context, and basket. No tool appears redundant, and the set is appropriately scoped for a specialized market intelligence server.
The read-only surface covers onboarding and three major data views (signals, context, basket), which is likely complete for a public market data API. Minor gaps include no explicit historical or per-asset query tool, but core workflows are covered.