Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOGS_DIRNoDirectory for log file storage (if LOG_OUTPUT_MODE=file).logs/
MCP_AUTH_MODENoAuthentication mode for HTTP: jwt or oauth.jwt
MCP_HTTP_HOSTNoHost address for the HTTP server (if MCP_TRANSPORT_TYPE=http).127.0.0.1
MCP_HTTP_PORTNoPort for the HTTP server (if MCP_TRANSPORT_TYPE=http).3010
MCP_LOG_LEVELNoLogging level (debug, info, notice, warning, error, crit, alert, emerg).info
LOG_OUTPUT_MODENoLogging output mode: file or stdout.file
MCP_TRANSPORT_TYPENoTransport mechanism: stdio or http.stdio
MCP_ALLOWED_ORIGINSNoComma-separated list of allowed origins for CORS (if MCP_TRANSPORT_TYPE=http).
MCP_AUTH_SECRET_KEYNoRequired for jwt auth. Minimum 32-character secret key for JWT authentication.

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

Tools

Functions exposed to the LLM to take actions

NameDescription
pubchem_search_compoundsA

Search PubChem for chemical compounds by identifier (name, SMILES, or InChIKey, up to 25 per call), molecular formula in Hill notation, substructure or superstructure containment, 2D Tanimoto similarity, or the compounds a bioassay (AID) found active or tested. Returns a page of CIDs — reach matches past maxResults with offset. Optionally hydrate results with properties to avoid a follow-up pubchem_get_compound_details call.

pubchem_get_compound_detailsA

Get detailed compound information by CID. Returns physicochemical properties (molecular weight, SMILES, InChIKey, XLogP, TPSA, etc.), optionally with a textual description (pharmacology, mechanism, therapeutic use), known synonyms, drug-likeness assessment (Lipinski/Veber rules), and/or pharmacological classification (FDA classes, MeSH classes, ATC codes). Fetches up to 100 CIDs per call; CIDs past that are returned in unprocessed for a follow-up call.

pubchem_get_compound_imageA

Fetch a 2D structure diagram (PNG image) for a compound by CID.

pubchem_get_compound_3d_structureA

Get a compound's default 3D conformer — atomic coordinates and bonds — for one CID. format="json" (default) returns atoms and bonds parsed into structured fields; format="sdf" returns the raw V2000 SDF text for passthrough to docking, rendering, or conformer tools. Optionally lists alternate conformer IDs. Not every compound has computed 3D coordinates (large molecules, mixtures, and some salts do not).

pubchem_get_compound_xrefsA

Get external database cross-references for a compound: PubMed citations, patent IDs, gene/protein associations, registry numbers, and taxonomy IDs. Results are paged per type — capped at maxPerType with the total count reported; reach the IDs past a page with offset. PubMed IDs come highest (most recently assigned) first and the other numeric types in ascending order; string IDs keep PubChem's order.

pubchem_get_compound_safetyA

Get GHS (Globally Harmonized System) hazard classification and safety data for one or more compounds by CID. Returns signal word, pictograms, hazard statements (H-codes), and precautionary statements (P-codes) per compound, merged across sources, plus each source's own classification — its signal word, pictograms, H-codes with ECHA notifier agreement percentages, and notification counts — since sources often disagree. Reports ECHA "Not Classified" verdicts as their own status.

pubchem_get_bioactivityA

Get a compound's bioactivity profile: which assays tested it, activity outcomes (Active/Inactive/Inconclusive), target identifiers (NCBI Gene ID, UniProt/GenBank accession), and quantitative values (IC50, EC50, Ki, etc.). Filter by outcome and/or a specific molecular target (NCBI Gene ID or protein accession) to focus the profile — e.g. "is this compound active against target T?".

pubchem_get_compound_interactionsA

Get a compound's interaction data: drug-drug interactions (DrugBank), drug-food interactions, and chemical-target interactions (binding/activity from BindingDB, ChEMBL, and others). Each entry carries its originating source. Results are paged per kind, with the source-record total and the next offset reported for each. Richest for approved drugs; many compounds have no deposited interaction records. Drug-drug and target interactions come from PubChem's SDQ service, which can refuse automated requests — a refused kind is reported in failedKinds while the others still return; per-target activity is also available from pubchem_get_bioactivity.

pubchem_search_assaysA

Find PubChem bioassays associated with a biological target. Search by gene symbol (e.g. "EGFR"), protein name, NCBI Gene ID, or UniProt accession. Returns a page of assay IDs (AIDs) — page past maxResults with offset — which can be explored further with pubchem_get_summary.

pubchem_get_summaryA

Get descriptive summaries for PubChem entities by ID. Supports assays (AID), genes (Gene ID), proteins (UniProt accession), and taxonomy (Tax ID). Up to 10 per call; identifiers past that are returned in unprocessed for a follow-up call.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 10 tools

Disambiguation4/5

Each tool targets a distinct data facet of PubChem (search, details, image, 3D, xrefs, safety, bioactivity, interactions, assays, summary), so boundaries are largely clear. The only mild overlap is between pubchem_get_bioactivity and pubchem_get_compound_interactions (both surface target activity) and details vs. summary, but descriptions clarify the intended split.

Naming Consistency5/5

All tools follow a consistent pubchem_<verb>_<noun> pattern (pubchem_search_*, pubchem_get_compound_*, pubchem_get_summary), with uniform snake_case and only get/search as verbs. The convention is predictable and readable throughout.

Tool Count5/5

10 tools is well-scoped for a large multi-faceted database like PubChem, with each tool earning its place across the compound/bioassay/target domains. No redundancy or padding.

Completeness4/5

Covers a broad read-only surface: compound search (name/SMILES/formula/substructure/similarity), details, image, 3D, xrefs, safety, bioactivity, interactions, plus assay search and entity summaries. Minor gaps exist (e.g., no dedicated gene/protein/taxonomy detail endpoint beyond the generic summary), but core workflows are well supported.

Maintenance

ActivityMaintained
ResponsivenessWithin a week