Skip to main content
Glama
PDBe MCP Servers

PDBe MCP Servers

Official
by PDBeurope

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NEO4J_URLNoThe Neo4j database URL (e.g., bolt://localhost:7687). Required for the graph server.
TOON_ENABLEDNoEnable experimental TOON-formatted output (optional). Set to 'true' to enable.
NEO4J_DATABASENoThe Neo4j database name (optional).
NEO4J_PASSWORDNoThe Neo4j password. Required for the graph server.
NEO4J_USERNAMENoThe Neo4j username. Required for the graph server.

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

Tools

Functions exposed to the LLM to take actions

NameDescription
ebi-pdbe-similar_ligands_comp_similarity_hetcode_64e4dc75B

Returns chemical components that are similar to the given chemical component. Results include stereoisomers, components sharing a common scaffold, and molecules with ≥60% PARITY score-based similarity.

ebi-pdbe-comp_intx_comp_intx_hetcode_8fee3085B

Returns aggregated interaction counts for protein-ligand interactions, derived from all PDB structures containing the given chemical component. The response reports how frequently a ligand atom interacts with specific amino-acid residues across the PDB, grouped by interaction type.

ebi-pdbe-comp_intx_proteins_comp_unip_hetcode_b6c68ca3B

Returns the protein chains in PDB entries that interact with the given chemical component and are mapped to UniProt, including the associated UniProt metadata for these proteins.

ebi-pdbe-ent_chain_seq_seq_id_chain_id_89a4956cA

Returns the amino-acid sequence for a specific PDB Entry and Chain ID (label_asym_id).

ebi-pdbe-tunnels_tunnels_id_138286ffA

Returns MOLE tunnel annotations for a PDB entry. When assembly_id is omitted, the PDBe-preferred assembly is used.

ebi-pdbe-funpdbe_for_ent_funpdbe_id_b44be798A

Returns a list of FunPDBe functional annotation resources available for a given PDB Entry, including their origin (e.g: “3Dcomplex”, “WEBnma”, “canSAR”), the annotation labels they provide (e.g: “Surface_residue”, “pocket_1”, “LP/P”), evidence ontology codes (e.g: ECO_0000053), release dates (e.g: 01/06/2017), and source URLs (e.g: https://prankweb.cz).

ebi-pdbe-specific_fafefar_id_4cd60ce4B

Returns all FunPDBe functional annotations and related metadata for each annotated residue or functional site of a given PDB entry ID for a specific FunPDBe annotation resource. Includes the evidence ontology codes (e.g: ECO_0000053), release date (e.g: 01/06/2017), and source URLs (e.g: https://prankweb.cz). Raw scores, confidence scores and confidence classification labels are also provided for each residue level annotation when possible.

ebi-pdbe-bound_molecules_bound_molecules_id_433acab7A

Returns information for all bound molecules for a given PDB entry ID, including carbohydrate polymers. Details include each Bound Molecule IDs (e.g: “bm1”, “bm2”), composition (covalently bound ligands with unique CCD IDs) and internal connectivity, or which bound are covalently bound together (e.g: [“F1”, “F6”] means bound ligands identified by author_residue_number “1” and “6” in chain_id “F” are covalently bound).

ebi-pdbe-bound_mibmiib_id_9eb5b2d0A

Returns composition and high-level interactions for a specific Bound Molecule ID (e.g., “bm1”) of a PDB entry ID. This includes its full composition (all covalently linked ligands with their CCD IDs), internal connectivity between those ligands (e.g: [“F1”, “F6”] means bound ligands identified by author_residue_number “1” and “6” in chain_id “F” are covalently bound), and all detected interactions between the bound molecule and surrounding residues or ligands (e.g., covalent, hydrogen-bond, polar, van der Waals, hydrophobic, and atom-plane interactions) calculated for the preferred assembly of the PDB entry.

ebi-pdbe-mol_cbliicis_id_c117dabcC

This call provides interactions for a bound ligand found in the entry.

ebi-pdbe-seq_cescie_id_5a830e8eB

Returns residue-level sequence conservation data for a specified PDB entry ID and PDB entity ID, including per-residue conservation scores and amino-acid probability distributions.

ebi-pdbe-unip_map_ent_unip_map_id_entity_id_ce7aaa0cB

Returns UniProt mappings for a specific PDB Entity ID, including matched UniProt accessions, residue-level alignment ranges, and metadata identifying the corresponding Best Chain ID for the mapping.

ebi-pdbe-sec_struct_ent_sec_struct_id_entity_id_04ac5bc3B

Returns secondary-structure annotations for a specified PDB Entity ID, including helices and strands, plus per-residue structural predictions from external tools (e.g., disorder, folding propensity, flexibility), each with associated scores, labels, and source metadata.

ebi-pdbe-bind_sites_ent_bind_sites_id_entity_id_efd81d99B

Returns ligand-binding site annotations for a specified PDB entity, including metadata such as Best Chain ID, Scaffold ID, and the total number of protein residues that interact with each ligand (based on ARPEGGIO). For each ligand, the endpoint provides its CCD ID, name, and a list of interacting residues grouped by the Bound Molecule ID they interact with.

ebi-pdbe-iface_res_ent_interfaces_id_entity_id_49a0e419A

Returns protein–protein interface annotations for a specified PDB Entity ID, identifying all residues that form PISA-detected contacts with interacting partner proteins. For each partner, the endpoint provides its UniProt accession, name, and the corresponding interface residue ranges, along with metadata such as the entity’s Best Chain ID.

ebi-pdbe-annot_ent_annot_id_entity_id_e5718131A

Returns residue-level functional and biophysical annotations for a specified PDB Entity ID, aggregated from multiple PDBe-KB partner resources (e.g., SASA, hydrophobicity, disorder, flexibility, EM local resolution). Data returned includes annotation type, per-residue scores, confidence metrics, group labels, and the originating resource URL, as well as the Best Chain ID for the entity.

ebi-pdbe-doms_ent_doms_id_entity_id_17aad3ceB

Returns sequence and structural domain annotations for a specified PDB Entity ID, including domain boundaries, identifiers, and names from CATH, SCOP 1.75, Pfam and InterPro domain resources, along with metadata such as the entity’s Best Chain ID.

ebi-pdbe-chains_ent_chains_id_entity_id_200017f6A

Returns detailed chain-level annotations for a specified PDB Entity ID, including all of their polymer chains, their residue ranges, and per-residue validation information, along with metadata such as Best Chain ID and author-provided chain identifiers (Obs: chainId in additionalData response refers to struct_asym_id not the author-provided auth_asym_id).

ebi-pdbe-var_ent_var_id_entity_id_777d29d4A

Returns UniProt sequence-variation annotations for a specified PDB Entity ID, remapped to the entity’s residue positions. The response includes each mapped UniProt accession and its variant features, such as variant type, alternative sequence, position, associated evidence, cross-references, clinical or functional annotations, and any available structural-impact metadata.

ebi-pdbe-assembly_ent_assembly_id_f7cff679A

Returns information for all assemblies of a specified PDB ID, with details provided for each constituent entity within every biological or author-defined assembly. For each assembly, the endpoint reports the molecular weight, entity types and names, chain mappings (note: the in_chains field lists struct_asym_id values rather than author-assigned chain identifiers), and the number of copies of each entity.

ebi-pdbe-ligand_monomers_ent_ligand_monomers_id_6ad4dfe8A

Returns all modeled non-water ligand instances for a PDB entry, including molecular weight, chain identifiers, residue numbers, chemical component IDs and names, PDB Entity IDs, conformer counts, Bound Molecule IDs, and functional annotations (cofactor-like, drug-like or reactant-like).

ebi-pdbe-molecules_ent_molecules_id_1cb4fd01B

Returns summarised detailed information about each molecule (or entity in mmcif-speak) in a specified PDB entry, including entity type; molecule names mapped from UniProt; the synonym field (equivalent to _entity.pdbx_description) for polymeric entities; DrugBank-derived synonyms for ligands; sequence data; chain assignments; copy numbers; source organism and sample preparation details; and ligand or chemical component information.

ebi-pdbe-ent_rlerl_id_2439bcf6A

List all residues in a PDB entry, excluding waters, including both modelled and unmodelled residues. For each residue, the response provides the entity ID, chain identifiers, mmCIF- and PDB-style residue numbers with insertion codes, chemical component names, the fraction of expected atoms that are modelled, and details of any alternate conformers present

ebi-pdbe-ent_iface_res_ent_iface_res_id_e3f93cbfA

Returns all interface residue contacts calculated by PISA (Proteins, Interfaces, Structures and Assemblies) for a specified PDB entry ID. The results include interaction types (e.g., salt bridges and hydrogen bonds), interatomic distances, and details of the participating atoms and residues from both interacting chains. Results can optionally be filtered by assembly_id and interface_id.

ebi-pdbe-ligand_sum_comp_sum_hetcode_e2f08774B

This call returns a summary for the chemical component identified by the given hetcode, including its chemical structure identifiers, physico-chemical descriptors, synonyms, PDB chemical component metadata, functional annotations, and cross-references to external resources.

ebi-pdbe-comp_in_comp_in_hetcode_e47e47bdA

This call returns a list of PDB entries that contain the given chemical component as defined in the PDB Chemical Component Dictionary. The list includes PDB entries where the component appears either as a standalone chemical component or as part of a larger entity.

ebi-pdbe-sum_qsvsqse_id_40d9190eB

These scores are harmonic means of percentile-based quality metrics for macromolecular structures: - geometry_quality: from geometric percentiles (Ramachandran, clashscore, sidechains). - data_quality: from diffraction–data percentiles (R-free, RSRZ). - overall_quality: combines geometry and data percentiles. If any contributing percentile is 0, the harmonic mean is 0. If all percentiles are unavailable, the score is null. experiment_data_available indicates whether experimental diffraction data were used

ebi-pdbe-key_val_stats_val_key_val_stats_ent_id_27bd5d60B

Provides a validation summary listing key geometric and electron-density–based metrics. For each category (e.g., bonds, angles, RNA suite, Ramachandran, sidechains, RSRZ), the report includes: - number of residues/instances checked - number of outliers - percent outliers - and, where applicable, RMSZ values. Categories with no relevant residues return null percentages.

ebi-pdbe-outliers_val_outliers_all_id_b2720a4aA

Lists all geometric and model–data outliers detected by MolProbity, grouped by category (e.g., clashes, sidechains, RSRZ, bond/angle outliers, RNA suite/pucker, chirality, planes, symmetry clashes). Atoms or residues involved in each outlier are reported using unit-id notation The types_of_outliers section summarizes, per residue, which types of outliers it participates in.

ebi-pdbe-ligand_mvvlmeiccirnr_number_339fc3c2B

Provides ligand-level validation results, combining Mogul geometric analysis (bond and angle RMSZ and atom outliers) with experimental fit metrics (OWAB, RSCC, RSR, LLDF, occupancy). Each returned ligand entry includes its location identifiers (entity, chain, residue, model) plus a flag indicating whether the ligand is an experimental outlier.

ebi-pdbe-best_soubsu_acc_11b902cfA

Provides a ranked list of PDB structures mapped to the given UniProt accession based on an internal quality score (based on data quality, model quality and resolution ). Each structure entry includes the experimental method, taxonomic origin, resolution, PDB ID and chain, entity and assembly identifiers, observed UniProt alignment segments, model residue ranges, and computed coverage of the UniProt sequence.

ebi-pdbe-best_nosoubnosu_acc_bf133eeeA

Retrieve a list of non-overlapping PDB chains that cover the largest number of observed residues for a given UniProt accession.

ebi-pdbe-unip_giruiru_acc_66c74d5cB

Retrieve detailed information on interface residues for a given UniProt accession, including the amino acid sequence for polymeric entities and the total sequence length. The response provides the type of data included and an array of residue-level details, with information such as the starting position in a processed protein sequence when applicable. This endpoint enables analysis of residues involved in protein interfaces, offering sequence context alongside structural and functional annotations.

ebi-pdbe-unip_ipuipu_acc_09a395aeB

Retrieve information on interaction partners for a given UniProt accession, including their names, annotations such as antibody roles, the PDB structures where interactions are observed, and whether the interaction is self-directed. This endpoint provides structural and functional context for protein interactions.

ebi-pdbe-unip_gen_unipdb_unip_unipdb_unip_acc_bf823946B

Retrieve comprehensive information on PDB structures mapped to a given UniProt accession. The response includes the UniProt sequence and length, along with detailed structure annotations such as entity and chain identifiers, residue coverage in UniProt and PDB numbering, observed regions, mutations, modifications, experiment type, resolution, ligand and entity counts, and supporting metadata like titles, ranking scores, and additional structure-specific information. This endpoint provides an integrated view of how PDB structures align with and represent the UniProt sequence

ebi-pdbe-unip_gen_annot_unip_annot_unip_acc_16305178A

This call provides PDBe-KB annotations for a given UniProt accession, with optional filtering by annotation category. The response includes the UniProt sequence and length, along with detailed annotation records describing residue ranges in UniProt and PDB numbering, residue codes, associated PDB entries, and supporting metadata such as accession identifiers, scores, confidence levels, and resource links. Information on processed protein start positions is also provided, offering a unified view of structural and functional annotations across the sequence.

ebi-pdbe-seq_cuuscu_acc_a66a4f59A

Retrieve PDBe-KB sequence conservation data for a UniProt accession. The response provides residue-level conservation scores, per-residue amino acid probability profiles, sequence identifiers, the length of the UniProt sequence, and colors for visualizing main and sub-tracks.

ebi-pdbe-unip_var_unip_var_unip_acc_6a476541B

Retrieve variation details for a given UniProt accession. The response includes the protein sequence and length, UniProt identifiers, and a list of variant features with information on alternative sequences, associated diseases, evidences, genomic locations, consequence types, and predictions from tools such as PolyPhen and SIFT. Additional metadata includes clinical significance, source information, cross-references, and relevant URLs, enabling comprehensive analysis of protein sequence variations.

ebi-pdbe-llm_unip_sum_unip_llm_annot_sum_unip_acc_72bf192aB

Retrieve text mined annotations for a given UniProt accession. The response includes associated PDB structures, and residue-level annotations. The residue start and end positions follow either UniProt or PDB numbering. Each annotation details the provider, additional supporting data such as citations, entity type, textual evidence, annotator, and AI-generated confidence scores, enabling comprehensive exploration of machine-predicted functional and structural insights.

ebi-pdbe-maps_maps_acc_cb64101dA

Provides unified SIFTS residue-level mappings between PDB protein chains (auth_asym_id or struct_asym_id) and all major sequence and domain resources, including UniProt, Pfam, InterPro, CATH, SCOP, GO, Ensembl, and HMMER. Supports both PDB-to-identifier and identifier-to-PDB queries, returning the mapped residue segments and associated annotations for each resource.

ebi-pdbe-complex_complex_details_id_b0542507A

Retrieve information about macromolecular complexes, including participants, stoichiometry, oligomeric state, symmetry, representative structure, structural instances, bound macromolecules, and subcomplex/supercomplex relationships. Queries using UniProt/Rfam accessions or PDB IDs can return multiple matching complexes. Currently, queries using pdb_complex_id return richer annotations and more detailed assembly information than other identifier types.

ebi-pdbe-complex_bmscbmsc_id_02b199bdA

Retrieve an aggregated summary of small-molecule ligands observed across different structural instances of a given macromolecular complex. The response includes ligand names, functional annotations (such as cofactor-like, drug-like, and reactant-like), and occurrence counts based on PDB entries, chains, and ligand instances.

ebi-pdbe-complex_icic_id_6bdd9e61A

Retrieve related subcomplexes and supercomplexes based on macromolecular composition. Subcomplexes contain a subset of the query complex's components, while supercomplexes contain additional components. The response includes PDB Complex IDs, representative structures, relationship types, and shared or additional macromolecular participants.

ebi-pdbe-complex_ppcpapc_id_72a20a8cB

Retrieve PISA-calculated structural and energetic properties for different structural instances of a given macromolecular complex, including accessible and buried surface areas, dissociation free energy, dissociation entropy, dissociation area, and solvation energy gain. The response also includes the 5th and 95th percentile values for these properties across the available structural instances.

ebi-pdbe-rfam_nucleic_maps_acc_6e531e81B

This call returns all PDB entries and RNA chains that map to the specified Rfam accession, including the matched regions.

ebi-pdbe-get_ai_summaryA

Retrieve the pre-generated AI summary for a four-character PDB entry. Use this for an entry overview instead of writing a new summary. Returns the available summary sections and abstract key points, preserving inline reference markers and listing their PDBe source URLs and fields. A summary may not exist for every entry.

ebi-pdbe-search_schemaA

Retrieves the Solr search schema for the PDBe search service. You can use this tool to understand the structure and fields available in the PDBe search index. Once you have the schema, you can use it to construct more effective search queries and run the query using the run_pdbe_search_query tool. This tool returns a detailed schema of the Solr search index used by PDBe. The schema includes information about all the fields available for searching, along with their types, whether they are stored or indexed, and any relevant descriptions. Expected Output Format: A text representation of the search schema, formatted as a table with the following columns: - Field Name: The name of the field in the Solr schema. - Type: The data type of the field (e.g. string, integer, date). - Stored: Indicates whether the field is stored in the index (true/false). - Indexed: Indicates whether the field is indexed for searching (true/false). - Description: A brief description of the field and its purpose. The output will be structured in a way that is easy to read and understand, allowing users to quickly grasp the available search fields and their characteristics.

ebi-pdbe-searchA

Executes a search query against the PDBe Solr search service. This tool exposes common Solr query parameters directly so users can construct fielded queries, filter queries, field lists, facets, grouping, sorting, and pagination against the PDBe search index. IMPORTANT: query is passed to Solr as the raw q parameter. Use Solr query syntax such as *:*, pdb_id:1cbs, text:*kinase*, boolean clauses, ranges, and boosts as needed. IMPORTANT: the text field is a copy field that contains the full searchable text aggregated from the document. Use text:*<term>* when you want a broad wildcard text search. Expected Input Parameters: - query (string): Raw Solr query string passed as q. - fl (string or list of strings, optional): Solr field list. The legacy filters parameter is also accepted as an alias. - filters (list of strings, optional): Backwards-compatible alias for fl. - fq (string, object, list of strings, or list of objects, optional): Solr filter query or queries to narrow down the search results. Objects are converted to fielded filters, e.g. {"experimental_method": "X-ray diffraction"} becomes experimental_method:"X-ray diffraction". - sort (string, optional): The sorting criteria for the search results. - start (integer, optional): The starting index for pagination of results. - rows (integer, optional): The number of results to return. - facet (boolean, optional): Enable Solr faceting. - facet_fields (string or list of strings, optional): Field facets, sent as facet.field. - facet_queries (string or list of strings, optional): Query facets, sent as facet.query. - facet_limit, facet_mincount, facet_sort (optional): Common facet controls. - group (boolean, optional): Enable Solr grouping. - group_field (string or list of strings, optional): Grouping field, sent as group.field. - group_limit, group_offset, group_sort (optional): Common grouping controls. - params (object, optional): Additional Solr parameters to pass through for advanced use.

Example Input:
{
    "query": "text:*kinase*",
    "fl": ["pdb_id", "title", "deposition_date"],
    "fq": ["experimental_method:\"X-ray diffraction\""],
    "facet": true,
    "facet_fields": ["experimental_method"],
    "sort": "deposition_date desc",
    "start": 0,
    "rows": 10
}

Expected Output Format:
A text representation of the search results, formatted in a readable manner. The output will include:
- Metadata about the search results (e.g. number of documents found, start index).
- A list of documents matching the search query, with each document's fields and values clearly presented.
The output will be structured to facilitate easy interpretation of the search results, allowing users to quickly identify relevant information.
        
ebi-pdbe-graph_nodesA
Retrieves metadata about all node types (also known as "labels") defined in the PDBe (PDBe-KB) graph database schema.
This tool can be used to understand the different types of entities represented in the PDBe graph database, along with
their properties and descriptions and then can be used to explore the graph more effectively by writing Cypher queries.
This tool returns detailed information about each node label in the graph database. For every node label, it includes:
- The label name (e.g., 'ValAngleOutlier', 'Antibody', 'Atom')
- A human-readable description of the node type
- A list of properties/parameters associated with this node type
- For each property: the name and a brief description

Expected Output Format (text):
Label: ValAngleOutlier
Description: Bond angle outliers based on wwPDB validation data.
Properties:
  - ATOM0/1/2/3: Names of atoms involved in the angle which is an outlier.
  - MEAN: The ideal value of the bond angle.
  - OBS: The observed value of the bond angle.

(Additional node labels follow the same format...)
ebi-pdbe-graph_edgesA
Retrieves metadata about all relationship types (edges) defined in the PDBe (PDBe-KB) graph database schema.
This tool can be used to understand the different types of relationships represented in the PDBe graph database, along with
their start and end nodes, properties and descriptions and then can be used to explore the graph more effectively by writing Cypher queries.
This tool returns detailed information about each relationship (edge) in the graph. For every relationship type, it includes:
- The relationship label (e.g., 'HAS_OUTLIER', 'CONNECTS_TO')
- A human-readable description of the relationship
- The 'from' node label and 'to' node label, defining the direction and connectivity
- A list of properties associated with the relationship
- For each property: the name and a brief description

Expected Output Format (text):
Label: HAS_OUTLIER
Description: Indicates a structure has validation outliers
From: Structure
To: ValAngleOutlier
Properties:
  - since: The date when the outlier was detected
  - severity: The severity level of the outlier

(Additional relationship types follow the same format...)
ebi-pdbe-graph_node_relationshipsA
Verifies one or more PDBe graph node labels and returns the relationships connected to each label.
Use this tool after inspecting the node and edge schema, when you have selected node labels for a Cypher query
and want to confirm that the labels and relationship directions exist in the PDBe graph schema.

For each requested node label, this tool returns:
- Whether the node label exists in the schema
- Outgoing relationship patterns from that node label
- Incoming relationship patterns to that node label
- Self-loop relationship patterns where both ends use the same node label
- A bidirectional note when the schema has the same relationship label in both directions between two node labels

Parameters:
    node_labels (required): A list of exact, case-sensitive node labels to verify.
        Example: ["Entry", "Entity", "UniProt"]

Expected Output Format (text):
Node: Entry
Status: Found
Outgoing edges:
  - (Entry)-[:HAS_ENTITY]->(Entity)
Incoming edges:
  - None
Self-loop edges:
  - None

Node: FakeNode
Status: Not found in schema
ebi-pdbe-graph_example_queriesA
Retrieves example Cypher queries for exploring the PDBe (PDBe-KB) graph database.
This tool can be used to get sample queries that demonstrate how to interact with the PDBe graph database using Cypher.
The tool returns a list of example queries, each with an question describing the purpose of the query and the corresponding Cypher query string.
Expected Output Format (text):
Question: Give me all the structures that are released in 2025.
Query:
MATCH (entry:Entry)
WHERE entry.PDB_REV_DATE STARTS WITH '2025'
RETURN entry.ID as PDB_ID,
    entry.TITLE as Title,
    entry.PDB_REV_DATE as Release_Date,
    entry.RESOLUTION as Resolution,
    entry.METHOD as Experimental_Method,
    entry.STATUS_CODE as Status
ORDER BY entry.PDB_REV_DATE DESC
(Additional example queries follow the same format...)
ebi-pdbe-graph_indexesA
Retrieves metadata about all indexes defined in the PDBe (PDBe-KB) Neo4j graph database schema.
This tool can be used to understand which node properties are indexed in the graph database, which is helpful
when writing Cypher queries to ensure indexes are properly utilized for optimal performance.

This tool returns detailed information about each index in the graph database. For every index, it includes:
- The node label that the index applies to (e.g., 'Entry', 'Pfam', 'UniProt')
- The property name that is indexed (e.g., 'ID', 'PFAM_ACCESSION', 'ACCESSION')

Expected Output Format (text):
Node: Entry
Property: ID

Node: Pfam
Property: PFAM_ACCESSION

Node: UniProt
Property: ACCESSION

(Additional indexes follow the same format...)
ebi-pdbe-update_workspaceB

Compose or restore a molecular workspace in the shared viewer. Supply the latest complete workspace from tool results or App context, expected_revision, and atomic operations. Supports adding/removing scenes and structures, component or annotation layers, and changing layer visibility. IDs must match exactly. No operations validates and restores a saved workspace. No global server state is stored. The host must route matching workspace IDs to an existing App for cross-call updates; otherwise a new viewer opens. The App displays supplied coordinates, transforms, residue mappings and annotations; it does not calculate scientific measurements.

ebi-pdbe-build_mvs_storyA

Build a guided molecular story with 2–20 ordered scenes and open it in Mol* 5.13.1. Each scene has a unique id, title, description and complete builder specification using the same schema as build_mvs. Set component opacity inside representation.opacity, never directly on a component. Ground all narrative claims and selections in PDBe evidence. Returns one native multi-state MVSJ with timed playback, scene navigation and download. The host can update the originating viewer or open a new result. Default duration is 6500 ms per scene and camera transition is 1500 ms. Stop after a compiled result. On validation failure, correct the input and retry once; never repeat identical input. Compilation does not establish coordinate availability or verify biological claims.

ebi-pdbe-build_mvsA

Build a custom single-scene molecular visualization with MolViewSpec and open it in Mol* 5.13.1. Supply a complete builder specification, including existing choices for follow-up changes; the host routes each result to an existing viewer or a new one. Supports chains, residue ranges, ligand instances, representations, colors, opacity, inline annotations, labels, tooltips, focus and camera. Set component opacity inside representation.opacity, never directly on a component. Ground selections in PDBe data; use label_seq_id for polymer residues and auth_seq_id with insertion code for non-polymers. Water is excluded from broad all selections unless include_water=true. Supports density isosurfaces and clipping; structure transforms/instances, multiple structures per scene, annotation tables, primitives and serialized MolQL selectors. No raw MVS trees, executable code or PyMOL text. Returns the complete normalized builder in structuredContent for follow-ups; full MVSJ is delivered to the App with download support. A compiled result completes the build; do not rebuild while waiting for viewer loading. Compilation does not verify biological claims or coordinate availability.

ebi-pdbe-compare_structuresA

Compare two protein label chains using PDBe's precomputed superposition matrices and SIFTS residue correspondence. Requires a shared UniProt accession and PDBe segment containing both chains. Opens aligned proteins first; ligands and residue annotations are opt-in through include_ligands/include_annotations or the workspace controls. Includes PDBe/SIFTS correspondence and CSV export. The viewer applies PDBe's transforms; no additional fitting, RMSD, per-residue displacement or inferred binding sites are calculated.

ebi-pdbe-open_structureA

Open an experimental PDB structure in an interactive 3D viewer. Inspect chains, ligand instances and residues. Displays the first coordinate model; defaults to the deposited asymmetric unit. A successful result completes the viewing request; stop calling this tool and let the App load coordinates.

ebi-pdbe-load_structure_annotationsA

Internal App-only helper; never call this in response to a user's request to open, view, inspect, or show a structure or PDB entry, including when they provide only an entry ID. For every initial structure-viewing request, call ebi-pdbe-open_structure. This helper is only for the App to load optional PDBe-supplied residue annotations into a workspace that is already open. Returns annotation records and track layers only, not coordinates or an MVS scene.

ebi-pdbe-ligand-interactionsA

Explore PDBe-reported interactions for an exact ligand instance in the shared Molecular Workspace. First call with a PDB ID to list instances; then provide author chain and author residue number (plus CCD and insertion code when available) to retrieve that instance's supplied interaction records. The App displays source classifications and distances without calculating or reclassifying contacts. Contact lines are shown only when atom and assembly/model mapping is unambiguous; otherwise use the table.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
PDBe Molecular Workspace
PDBe Structure Explorer
PDBe Structure Comparison Workbench
PDBe Custom Molecular View
molview-specBuild or replace custom molecular views and guided molecular stories with PDBe evidence and MolViewSpec, or explore PDBe-reported ligand interactions in the Molecular Workspace. Use for explicit visualization, representation, coloring, highlighting, ligand-contact, or story requests.
builder-api.md
molql-symbols.json
scene.schema.json
scenes.md
stories.md
story.schema.json

TDQS

B3.1/5.0

Scored across 60 tools

Disambiguation3/5

Many tools cover distinct PDBe resource levels (entry, entity, chain, ligand, UniProt, complex, validation, graph), and descriptions generally clarify their targets. However, several retrieval tools overlap conceptually—e.g. multiple ligand interaction tools, bound-molecule tools, and several sequence/annotation endpoints—while cryptic generated names make misselection likely in a 60-tool set.

Naming Consistency2/5

There is a shared `ebi-pdbe-` prefix, but the remainder is inconsistent: some tools use clean descriptive names like `search_schema`, `open_structure`, and `graph_nodes`, while many are auto-generated strings with embedded identifiers and hashes such as `seq_cuuscu_acc_a66a4f59` and `comp_intx_comp_intx_hetcode_8fee3085`. Hyphenated and underscored names are also mixed.

Tool Count2/5

The server exposes 60 tools, which is very heavy for an agent-facing toolset even though PDBe is a broad structural bioinformatics domain. Many endpoints appear to correspond to individual PDBe API resources, increasing selection burden and reducing practical usability compared with a more curated set.

Completeness4/5

Coverage is broad: search, entry-level summaries, entities/chains, sequences, ligands, interactions, validation, UniProt mappings, complexes, Rfam, graph schema helpers, and visualization/workspace tools are all represented. Some direct access patterns are missing or only reachable indirectly through search, but there are few obvious dead ends.

Maintenance

ActivityMaintained
ResponsivenessLimited data