Skip to main content
Glama
dnanatihor

Epistemic Envelope

by dnanatihor

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
EPIENV_INFERENCENoControls the inference policy that can drop AI inferences from the rendered output. Set to "off" (EPIENV_INFERENCE=off) to withhold AI inferences; otherwise model text is placed in the AI inferences layer.on

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

CapabilityDetails
tasks
{
  "list": {},
  "cancel": {},
  "requests": {
    "tools": {
      "call": {}
    },
    "prompts": {
      "get": {}
    },
    "resources": {
      "read": {}
    }
  }
}
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_assetsA

List tables and columns in the seed catalog.

get_asset_profileC

Return profiling observations, and inferences when policy allows them.

describe_assetB

Return quality results, profile, and inferences for one asset.

get_qualityB

Return certified data-quality findings for one asset.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 4 tools

Disambiguation2/5

list_assets is distinct, but get_asset_profile, describe_asset, and get_quality overlap: describe_asset returns profile, quality, and inferences, making the narrower tools seem redundant and boundaries unclear. An agent could reasonably choose describe_asset for most per-asset queries.

Naming Consistency5/5

All names use a snake_case verb_noun format: list_assets, get_asset_profile, describe_asset, get_quality. Verb choices vary naturally by action, with no mixed conventions.

Tool Count4/5

Four tools is a reasonable, focused count for a read-oriented catalog/quality server. It is slightly thin and includes some redundant coverage, but not too many or too few.

Completeness3/5

Core per-asset inspection is covered (list, profile, description, quality), but there is no catalog-level quality listing, search, or lineage/update operation. For a read-only epistemic catalog this is a notable gap, though not a severe failure.

Maintenance

ActivityMaintained
ResponsivenessNo issues