DriftScope
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 |
|---|---|
| generate_mock_datasetsB | Generates synthetic baseline and production CSVs in the local cloud storage. |
| check_feature_driftB | Evaluates covariate shift for a continuous feature between baseline and production datasets using the Kolmogorov-Smirnov (KS) test. Accepts both local file paths and public HTTP/HTTPS URLs. |
| get_monitoring_policyA | Returns organizational reference guidelines for drift and model monitoring thresholds. |
| compute_psiB | Computes Population Stability Index (PSI) to evaluate feature shift severity. Accepts both local file paths and public HTTP/HTTPS URLs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| audit_feature | Guides the model through a full statistical drift triage. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_drift_policy | Returns organization monitoring standards. |
TDQS
Scored across 4 tools
check_feature_drift and compute_psi both assess feature drift but with distinct statistical methods (KS test vs. PSI) and different outputs (shift detection vs. severity). This is a clear enough separation, though an agent might still pause to choose between them for a generic drift-check request. generate_mock_datasets and get_monitoring_policy are unambiguous.
All tools use a consistent verb_noun snake_case pattern: generate_mock_datasets, check_feature_drift, get_monitoring_policy, compute_psi. Minor abbreviation in compute_psi doesn't break the convention. The set is highly predictable.
Four tools are well-scoped for a focused drift analysis server: one data generator, two drift metrics, and one reference tool. Each tool clearly earns its place without redundancy. The count fits comfortably within the ideal 3-15 range.
The surface covers continuous feature drift via KS and PSI, plus data generation and policy guidelines. However, it lacks categorical drift tests, batch/multi-feature analysis, and any policy update or model drift tools. These are notable gaps for a server named DriftScope.