semantic-context-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HF_HUB_OFFLINE | No | Set to 1 to skip Hugging Face Hub freshness check once the model is already cached locally. Without this, the first search after startup needs network access. |
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 |
|---|---|
| search_tablesA | Find warehouse tables by describing what you want in plain English. Call this before writing SQL whenever you are not certain which table holds the data — table names alone do not tell you whether a table is current, correct, or maintained. Returns candidates ranked by relevance, each with its owner and status. Deprecated tables are included and labelled, so you can recognize them in existing queries rather than assuming they are fine. Args: query: What you are looking for, e.g. "daily net revenue" or "customer churn". limit: Maximum candidates to return (1-25). |
| describe_tableA | Get the full meaning of one table: purpose, grain, owner, status, and columns. Call this before using any table you have not already described in this
conversation. The column Args: table: Table name, fully qualified or bare (e.g. "main.fct_revenue_daily"). include_columns: Set False when you only need purpose, owner, and status. |
| trace_lineageA | Trace where a table or column's data comes from, and what depends on it. Call this when you need to justify a number, when a value looks wrong and
you need to find where it was computed, or before suggesting a change to a
table so you can say what it would break. Pass Args: table: Table name, fully qualified or bare. column: Optional column to trace; omit for table-level lineage. direction: "up" for sources, "down" for dependents, "both" (default). depth: How many hops to follow (1-5). |
| check_healthA | Check whether a table is safe to rely on right now. Call this before presenting any number derived from a table you have not already checked, and whenever a user mentions a table you did not choose yourself. Reports freshness, row-count movement, null rates, and dbt test results, plus a one-line verdict. A verdict of "deprecated" or "failing" means you should warn the user before using the table, not silently proceed. Args: table: Table name, fully qualified or bare. |
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
Each tool addresses a distinct aspect of table understanding: search finds tables by description, describe explains meaning and columns, trace_lineage maps data flow, and check_health assesses reliability. There is no overlap between these purposes, so an agent can cleanly select the right tool for the job.
All tool names follow a consistent verb_noun pattern with lowercase and underscores: search_tables, describe_table, trace_lineage, check_health. The verbs are specific and the nouns clearly indicate the target resource, making the API predictable.
Four tools is a tight, well-scoped set for a semantic context server focused on warehouse table understanding. Each tool covers a necessary capability without redundancy or bloat, fitting comfortably within the ideal 3-15 range.
The tool surface covers the complete workflow for exploring and validating tables: discover via search, inspect via describe, understand dependencies via lineage, and assess trustworthiness via health. There are no obvious missing operations that would force an agent to work around gaps.