Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
UV_TORCH_BACKENDNoSet to 'cpu' for CPU PyTorch packages instead of CUDA runtime packages in hosted Linux deployments.
CRC_LNM_MCP_RUNTIME_ROOTNoOptional. Specifies a writable cache location. Defaults to a system cache directory.

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
crc_lnm_get_model_infoB

Return integrity-checked model dimensions, version, hashes and threshold.

crc_lnm_case_data_qcB

Validate deidentified case integrity, privacy and required modalities.

crc_lnm_prepare_ct_featuresB

Validate and retain approved precomputed 1409-dimensional CT features.

crc_lnm_prepare_pathology_featuresC

Validate and retain approved 768-dimensional pathology features.

crc_lnm_predict_multimodalC

Run the locked five-member multimodal ensemble after compatibility gates.

crc_lnm_generate_reportC

Generate a deterministic escaped research-assistance report.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation5/5

Each tool serves a distinct pipeline stage: model info retrieval, case data QC, CT feature preparation, pathology feature preparation, multimodal prediction, and report generation. No two tools appear to handle the same responsibility, so an agent can unambiguously select the right tool for each step.

Naming Consistency4/5

All tools share the consistent 'crc_lnm_' prefix and use snake_case. Most follow a verb_noun pattern (get_model_info, prepare_ct_features, generate_report), though 'case_data_qc' is more noun-like and 'predict_multimodal' uses an adjective, creating minor deviations. Overall the naming is predictable and readable.

Tool Count5/5

Six tools cover the full end-to-end workflow of a specialized medical AI pipeline without redundancy. The count is appropriately scoped for the server's purpose, neither sparse nor bloated.

Completeness5/5

The tool set covers the complete workflow from model inspection and data QC through feature preparation, prediction, and report generation. There are no obvious gaps for the intended use case, as each step in the pipeline is represented.

Maintenance

ActivitySlowing
ResponsivenessNo issues