Skip to main content
Glama
PDBe MCP Servers

PDBe MCP Servers

Official
by PDBeurope

ebi-pdbe-unip_gen_unipdb_unip_unipdb_unip_acc_bf823946

Read-only

Retrieve PDB structures mapped to a UniProt accession, including sequence length, chain and residue coverage, mutations, modifications, experiment type, resolution, ligand counts, and metadata.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uniprot_accession": "<uniprot_accession>"
    },
    "name": "ebi-pdbe-unip_gen_unipdb_unip_unipdb_unip_acc_bf823946"
  }
}

Input Schema

NameRequiredDescriptionDefault
uniprot_accessionYesUniProt accession. title: Uniprot Accession description: UniProt accession.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.1

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral value by enumerating what the response contains (residue coverage, observed regions, mutations, resolution, ranking scores), but says nothing about pagination, error behavior for unknown accessions, or result volume for promiscuous accessions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is correctly front-loaded in the first sentence, but the second sentence is a long undifferentiated run-on list of return attributes and the third restates the same idea. The content is useful but not structured for scanning, and the trailing sentence is largely redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and only one input parameter, the description has to describe the payload, and it does so in unusually rich detail. Only the absence of guidance on result shape variability and sibling disambiguation keeps it below a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter with 100% schema description coverage, so the schema already carries the documentation burden and the baseline of 3 applies. The description adds no meaning about the accession itself, e.g. whether UniProt IDs are accepted alongside accessions or how isoforms are handled.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource: retrieve PDB structures mapped to a UniProt accession. That is far clearer than the opaque tool name, but it never distinguishes this tool from close siblings such as unip_gen_annot, unip_map_ent, or unip_giruiru/ipuipu, which operate on the same UniProt accession axis.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the closing line about providing an 'integrated view' of how PDB structures align with a UniProt sequence. There is no explicit statement of when to pick this over the many other unip_* siblings, and no prerequisites or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools