streamprobe-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| diagnose_streamA | Fetch a manifest and report what is wrong with it, worst first. Start here when a stream misbehaves and you do not yet know why. Set deep to also read each rendition's media playlist, which is required to catch segment timing and live window problems. |
| describe_streamA | The facts only: protocol, live or VOD, the rendition ladder, codecs, audio and subtitle tracks, protection and ad markers. Use when you want to know what a stream is rather than what is wrong with it. |
| inspect_drmA | Report the DRM systems, key identifiers and license URIs a manifest declares. Reads the manifest only: it never requests a license or attempts decryption. |
| check_segmentsA | Request the newest few segments of the first rendition and report failures and timings. Answers the case where the manifest is valid but the media behind it is missing or slow. Uses HEAD where the CDN allows it. |
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
diagnose_stream is intentionally broad as a triage entry point, while describe_stream, inspect_drm, and check_segments each target a distinct concern. Some overlap exists between diagnose_stream's deep mode and check_segments, but the descriptions clearly delineate when each should be used.
All tool names follow a consistent verb_noun pattern: diagnose_stream, describe_stream, inspect_drm, check_segments. The verbs are distinct and the objects clearly indicate the target of each operation.
Four tools is well-scoped for a stream diagnostics server. Each tool covers a meaningful facet of the domain—overall diagnosis, factual description, DRM inspection, and segment health—without unnecessary redundancy.
The set covers the main streaming diagnostics workflows: triage, stream description, DRM inspection, and segment validation. Minor gaps remain, such as check_segments only examining the first rendition and no tool for deeper per-track analysis, but the core surface is reasonably complete.