Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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.

Cleaned tables from the HIMC data room: a fictional UK hospital (Kingsmere), a fictional Kenyan county hospital (Kisima), a fictional Indonesian regional hospital (Sukamaju) and the back-test of a fictional bed-forecasting prototype. All of this data is fictional teaching material: the company, the three hospitals and every person in it were invented. Say so when you report a result, and never present a finding as true of a real hospital. Start with overview, then list_tables and describe_table, then query with SQLite SQL. Answer the question asked from the data, show the numbers and the table they came from, and do not volunteer conclusions or recommendations the user did not ask for. Columns starting dq_ flag data-quality problems (1 = problem present); *_raw columns hold the value before correction. Check data_quality_log before trusting a trend.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
overviewA

What the tables are, how the data was cleaned and the caveats to respect before analysing. Read this first.

list_tablesA

Every table with its row and column counts. Table names are <hospital>__<table>, e.g. uk_kingsmere__daily_site_panel.

describe_tableB

Columns (name and type), row count, three sample rows, and which columns are data-quality flags, for one table.

queryA

Run one read-only SQLite SELECT (or WITH ... SELECT) and get the rows back.

Aggregate in SQL instead of pulling raw rows: the stays table has 151,000 rows. At most 1,000 rows are returned; truncated says whether more existed. Dates are text in YYYY-MM-DD form, so strftime('%Y-%m', date) and date BETWEEN '2025-11-01' AND '2026-10-31' work.

data_quality_logA

The 53 problems found while cleaning: what was wrong, how many rows, what was done, how it was found. Pass dataset (e.g. "uk.spells", "ke.bed_state") to see one table's issues, or part of a name such as "uk".

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 5 tools

Disambiguation4/5

Each tool has a distinct role: overview for orientation, list_tables for discovery, describe_table for schema detail, query for execution, and data_quality_log for cleaning provenance. The only mild overlap is between overview and data_quality_log, since both discuss how the data was cleaned, though one is dataset-wide narrative and the other is per-table issue logging.

Naming Consistency4/5

All names are snake_case and readable, with list_/describe_ verb prefixes on the discovery tools. query, overview, and data_quality_log are noun/single-verb forms rather than verb_noun, a minor deviation but nothing confusing.

Tool Count5/5

Five tools is well-scoped for a read-only analytical dataset server: discovery, inspection, execution, and two context tools. Nothing feels padded and every tool earns its place in the exploration workflow.

Completeness4/5

The surface covers the full read-only lifecycle: orient (overview), discover (list_tables), inspect (describe_table), query (query), and audit provenance (data_quality_log), with SQL handling joins and aggregation. Minor gaps include no schema-wide search or column-level lookup, but agents can work around these with query.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues