Spyglass AI MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPYGLASS_API_KEY | Yes | API Key for authentication with Spyglass agent | |
| SPYGLASS_AGENT_ENDPOINT | No | Agent endpoint URL (useful for local testing) | https://agent.spyglass-ai.com |
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| call_spyglass_agentA | Call the Spyglass AI agent with a natural language query about your telemetry data. Args: query: Natural language query about telemetry data (e.g., "What are the slowest endpoints?") Returns: Analysis result from the Spyglass AI agent |
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
Only one tool exists, so there is no possibility of ambiguity between tools.
The single tool name 'call_spyglass_agent' follows a clear verb_noun pattern, which is consistent and descriptive.
A single tool for telemetry data analysis feels thin; typical telemetry servers offer multiple operations (e.g., list, get, query).
The tool only allows querying via an AI agent, with no tools for data exploration, configuration, or management, leaving significant gaps in the expected functionality.