pdbe-api

Fetch PDBe structure data and search results from within Coot.

166|59|Updated Aug 24, 2015
One-click install
npx skills add https://github.com/pemsley/coot --skill pdbe-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pdbe-api
Source: https://github.com/pemsley/coot/tree/main/mcp/docs/skills/pdbe-api
Command: npx skills add https://github.com/pemsley/coot --skill pdbe-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables querying the PDBe REST and Solr APIs from within Coot to access structure metadata, validation data, revision history, and search capabilities.

Core Features & Use Cases

  • PDBe REST access: Retrieve structure summaries, validation reports, and revision details directly inside Coot.
  • Ligand and compound data: Fetch information on ligands, compounds, and their metadata for quick analysis.
  • Solr search integration: Run advanced PDBe search queries to discover related structures, assemblies, and bindings.

Quick Start

From within Coot, fetch the PDBe structure summary for 4wa9 using coot_get_url_as_string_py and parse the JSON response.

Frequently Asked Questions about pdbe-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve PDBe structure summaries and validation reports from within Coot?

Query PDBe ligand and compound information in Coot by constructing a REST API URL and parsing the JSON response returned by coot_get_url_as_string_py to extract ligand metadata.

Can I run advanced PDBe Solr search queries to discover related structures inside Coot?

Run advanced PDBe Solr search queries inside Coot to discover related structures, assemblies, and bindings by constructing search URLs and parsing the returned JSON results.

How do I handle URL construction and error handling when fetching PDBe data via REST?

Handle URL construction and error management for PDBe REST queries by validating the endpoint strings passed to coot_get_url_as_string_py and managing exceptions when parsing JSON responses.

Does this PDBe API integration work without external Python dependencies in Coot?

The PDBe API integration works without external dependencies in Coot, relying solely on the built-in coot_get_url_as_string_py function to fetch REST and Solr JSON data.