Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NODE_EXTRA_CA_CERTSNoPath to a corporate CA certificate for TLS inspection when behind a corporate proxy.

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
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_codesA

Search the hospitals' own item descriptions (as published in their price files) for billing codes, e.g. 'mri brain' or 'office visit established'. Returns each code with the hospitals that publish it and their descriptions. Use the code with compare_code_prices or get_payer_rates.

compare_code_pricesA

Negotiated-rate summary (min, quartiles, max over payer plans) for one billing code at each hospital in the release, for one rate basis, with the hospital's source file cited on every row. Hospitals that publish the code differently are listed in not_included with what they do publish.

get_payer_ratesA

Every published charge for one billing code at one hospital: payer, plan, setting, negotiated rate (or the percentage/algorithm when no dollar figure is published), gross and cash price, with the charge's position in the hospital's source file. The first call downloads the 117 MB charge table once.

lookup_providerA

Look up a National Provider Identifier in the NPPES registry history: name, entity type, status, practice address and taxonomy as of a date (or now), every version on record, and whether a hospital in the release discloses it. Validates the NPI check digit first.

data_qualityA

Per hospital: whether the NPIs its price file discloses resolve to it in NPPES, how many of its NPIs it leaves undisclosed, how its file departs from the CMS template (and how often), and rows quarantined. Use it to qualify any price answer.

release_infoA

The pinned clear-pricer release this server answers from: its tag, the manifest hash it was verified against, the hospital price files and NPPES files it was built from, and each table's row count and status.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct resource and action: code search (find_codes), cross-hospital price comparison (compare_code_prices), single-hospital payer detail (get_payer_rates), provider lookup (lookup_provider), data quality checks (data_quality), and release metadata (release_info). No overlapping responsibilities; the descriptions clarify the boundaries between price-related tools.

Naming Consistency4/5

All names use snake_case and follow a verb_noun or noun_noun pattern, which is readable and consistent. Minor deviations: 'data_quality' and 'release_info' are noun phrases without a verb, unlike the others, but the overall convention is predictable.

Tool Count5/5

Six tools is well-scoped for a domain focused on hospital price transparency data. Each tool serves a clear purpose: discovery, comparison, detail, provider validation, quality assurance, and provenance. No tool feels redundant or missing.

Completeness4/5

The surface covers the core lifecycle: finding codes, comparing prices across hospitals, drilling into payer rates, validating providers, assessing data quality, and retrieving release info. Minor gaps include a possible tool for bulk or geographic search, but the current set handles typical agent queries effectively.

Maintenance

ActivityMaintained
ResponsivenessNo issues