Skip to main content
Glama

Rcsb Pdb Structure

rcsb_pdb_structure
Read-onlyIdempotent

"PDB entry [1abc] details" / "fetch protein structure [pdb_id]" / "metadata for [PDB ID]", full PDB entry record by ID (e.g. "1abc", "7BV2"). Returns experimental method (X-ray / cryo-EM / NMR), resolution, authors, deposition date, organism, ligands, related entities. Use after search to inspect a specific structure.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pdb_id": "1abc"
    },
    "name": "rcsb_pdb_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdb_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered; the description adds what the record actually contains (method, resolution, authors, deposition date, organism, ligands, entities), which is genuine context beyond the annotations. It does not mention error behavior for invalid or non-existent PDB IDs.

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

Conciseness4/5

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

The record type, scope and return fields are front-loaded in a single tight block, followed by a routing hint. The slash-separated query-phrase preamble is slightly noisy but serves a routing purpose and nothing is 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 an output schema present and annotations covering safety, the description need only establish purpose, input format and usage sequencing, all of which it does. Only invalid-ID behavior and differentiation from rcsb_pdb_summary are missing.

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

Parameters4/5

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

Schema coverage is 0% for the single pdb_id parameter, so the description must carry the format burden; it does so by giving concrete 4-character examples ('1abc', '7BV2') and describing the resource as an 'ID'. It could be sharper about accepted case or alternative ID formats (e.g. mmCIF), but the format is adequately conveyed.

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

Purpose5/5

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

States a specific verb and resource ('full PDB entry record by ID') with concrete ID examples ('1abc', '7BV2'), and distinguishes itself from the search sibling by framing it as the inspect-one-structure step. An agent can select it over rcsb_pdb_search without opening either schema.

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

Usage Guidelines4/5

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

Explicitly says 'Use after `search` to inspect a specific structure', which gives a clear sequencing rule and names the natural predecessor. It stops short of stating when not to use it or how it differs from the similarly-scoped rcsb_pdb_summary sibling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.