Strata
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STRATA_REPO_PATH | Yes | Path to your LookML repository. | |
| STRATA_USAGE_FIXTURE | No | Path to usage facts fixture JSON (optional, for offline mode). | |
| STRATA_SCHEMA_FIXTURE | No | Path to schema facts fixture JSON (optional, for offline mode). |
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 |
|---|---|
| strata_query_fieldD | – |
| strata_list_orphansD | – |
| strata_explore_depsD | – |
| strata_ir_statusD | – |
| strata_usage_summaryD | – |
| strata_dead_code_registerD | – |
| strata_pdt_costsD | – |
| strata_schema_driftD | – |
| strata_validation_scopeC | Determine blast radius for changes (impacted_views, impacted_explores, impacted_fields). |
| strata_impactB | Get the downstream impact of a physical table (physical_table, views, explores, fields). |
| strata_find_fieldB | Search for fields matching a query string across all views (query, kind, matches, count). |
| strata_view_sourcesC | List views and their resolved physical tables (model_filter, views, count). |
| strata_navigateA | Classify a ticket anchor and return a full navigator brief in one call. anchor: BQ table, field name, view, explore, or .lkml filename. Returns the views/explores/fields it touches with source_file:source_line citations, plus an inferred change type and what-to-touch list when ticket is set. |
| strata_list_skillsA | List available skills (name, domain, mode, complexity, trigger). |
| strata_skillA | Get the full SKILL.md content for a specific skill. |
| strata_conductor_statusA | Get the current Conductor workflow status (active_slice, next_steps, latest_handoff). |
| strata_chart_templatesA | List available Vega-Lite chart templates (name, mark). |
| strata_render_chartC | Render a chart using a Vega-Lite template and JSON data (path, status). |
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 18 tools
Several tools occupy overlapping impact/navigation territory: strata_impact, strata_validation_scope, and strata_navigate all return affected views/explores/fields, while strata_find_field and strata_query_field have similar search/query semantics. strata_list_orphans and strata_dead_code_register also blur together. Without more detailed descriptions, an agent could easily select the wrong tool.
All tools share the strata_ prefix and use snake_case, which provides a consistent namespace. However, the verb_noun pattern is not maintained: list_orphans and find_field sit alongside bare noun phrases like ir_status, pdt_costs, schema_drift, and conductor_status. The singular strata_skill also breaks the list/detail convention established by strata_list_skills.
18 tools is above the typical 3-15 well-scoped range and mixes core data-model analysis tools with meta utilities like skills, conductor status, and chart templates. It is not extreme, but the set feels heavier and broader than necessary for a focused server.
For a read-only data-model navigation and impact-analysis server, the surface covers discovery, dependency exploration, impact assessment, orphan/dead-code detection, schema drift, usage, costs, and even rendering charts. Minor gaps exist, such as no explicit per-explore detail tool and no apply flow after validation_scope, but agents can generally work around these.