Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_PORTNoPort for the HTTP daemon3163
BRAVA_DB_URLNoURL where to fetch the databasethe release asset
BRAVA_DB_PATHNoLocal path to the database~/.cache/brava-mcp/brava.duckdb
MCP_TRANSPORTNoTransport mode: 'stdio' for stdio, 'http' for the shared daemonstdio
BRAVA_VARIANT_BASE_URLNoBase URL for variant-level filesupstream R2

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
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
queryA

Run read-only SQL over the whole BRaVa gene-level results table.

61.8 million rows: every gene x trait x variant-mask x MAF-cutoff x ancestry cell, with the Burden, SKAT and SKAT-O p-values, the effect size and its standard error, and the cross-cohort heterogeneity test. Local, so a query costs no network.

Call schema() first. It returns the tables, the columns, worked query templates, and the semantic traps that make a syntactically valid query scientifically wrong here. Several of them invert the answer rather than degrade it.

Query the results view rather than the raw tables: it exposes p-values instead of -log10, and labels instead of integer codes, so the obvious query is also the correct one.

schemaA

The tables, the query templates, and the traps. Read this before querying.

Returns the shipped tables with their columns and row counts, worked queries for the questions people actually ask, the analysis vocabulary (masks, MAF cutoffs, tests, significance thresholds), and a list of ways a correct-looking query gives a wrong answer on this data. That list is not boilerplate: it covers effect sizes that belong to a different test than the p-value beside them, a mask that is a calibration control rather than a biological category, ancestry strata that overlap, and p-values of exactly zero that mean the most significant result rather than a missing one.

Returns: tables, columns, recipes, vocabulary, thresholds and pitfalls.

gene_phenotype_detailB

Does a gene-trait association replicate across ancestries and biobanks?

BRaVa's distinctive view, and a tool rather than a documented query because the concordance count has to exclude the two pooled strata ('All' and 'non_EUR') that contain the same individuals as the ones being counted. The obvious SQL double-counts and looks entirely reasonable.

Pass a comma-separated list to screen a whole hit list at once: one gene at a time costs a call each, the list form returns a verdict per gene. Verdicts separate "underpowered" from "discordant", which is the distinction that matters when a stratum is fifteen times smaller than another.

variantsA

Single-variant results for a trait, genome-wide or inside one gene.

Drops below the gene-level burden tests to the individual variants carrying a signal. Without gene this ranks the whole genome for the trait; with gene it restricts to that gene and adds the per-biobank effect-direction tally, the cross-biobank replication evidence.

Still fetched over HTTP rather than shipped in the database: the variant-level format is a separate, actively changing upstream release, an order of magnitude larger than the gene-level table, and rebuilt often enough that a local copy would be stale within the week. Each file is cached permanently once fetched.

Each row links to gnomAD, where population allele frequencies live.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/plemio/brava-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server