Skip to main content
Glama

Rcsb Pdb Summary

rcsb_pdb_summary
Read-onlyIdempotent

Lightweight lookup for a PDB entry by 4-char ID: tries the RCSB UniProt endpoint first, falls back to the core entry record. Returns title, experimental method, resolution, and deposition date without the full polymer/ligand detail of 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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdb_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 genuinely new behavioral detail — that it queries the RCSB UniProt endpoint first and falls back to the core entry record. That fallback sequencing is real information an agent cannot get from annotations. It does not describe error behavior when an ID is missing from both sources.

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

Conciseness5/5

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

Two sentences, front-loaded with the purpose, followed by the return scope and the sibling contrast. No filler, no restatement of the title.

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?

For a single-parameter read-only lookup with an output schema, this is nearly complete: purpose, ID format, return fields, retrieval strategy, and sibling differentiation are all present. Only the failure/not-found path is unaddressed, which is a small residual gap given the output schema handles return shape.

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% and the sole parameter is just `{"type":"string"}`, so the description must carry the meaning — and it does, specifying the ID must be a 4-character PDB ID and giving `1abc` as the schema example. It does not cover invalid-ID or not-found behavior, keeping it short of a 5.

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 ('Lightweight lookup for a PDB entry by 4-char ID') plus the exact shape of the return (title, experimental method, resolution, deposition date), and explicitly contrasts itself with the `structure` sibling. An agent can distinguish it from `rcsb_pdb_structure` 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?

Implies the selection rule clearly: use this when you want summary-level data rather than 'the full polymer/ligand detail of `structure`'. It names the heavier alternative and the condition that favors this tool, though it does not state an explicit 'use this when...' exclusion clause.

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.