Skip to main content
Glama
rcsb

io.github.rcsb/rcsb-mcp

Official
by rcsb

rcsb_list_pdb_search_attributes

Read-onlyIdempotent

List RCSB PDB search attribute paths, value types, and operators to find the exact attribute for your query.

Instructions

Discover the RCSB PDB Search schema: attribute paths, value types, and operators.

Call this FIRST when a request resolves to a clear attribute and value but you don't know the exact path; pick the attribute here, then use it in rcsb_search_by_attribute (or as an attributes entry on any rcsb_search_*).

Args: query: Optional case-insensitive keyword to filter the catalog. Matched as a LITERAL SUBSTRING against the attribute path and description, so pass ONE keyword ("resolution", "comp_id"), not a phrase — a multi-word query only matches where those exact words are adjacent in a description. Omit to return everything. schema: Which catalog — "structure" (~675 attrs: entry/entity/assembly/instance) or "chemical" (~57 attrs: chemical-component). See the server instructions for how to search chemical attributes.

Returns: {count, match_mode, attributes, note?}. attributes holds {attribute, type, operators, description} records — the RCSB/PDB attribute path (e.g. "rcsb_entry_info.resolution_combined"), its value type (string/number/integer/date), the operators it supports (exact_match, greater, range, exists, ...), and a human-readable description. match_mode is "exact" (the query matched), "none" (nothing matched — read note, the query shape is the usual cause), or "all" (query omitted, whole catalog).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
schemaNostructure

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations already declare readOnly=true, idempotent=true, etc., but the description adds significant behavioral nuance: case-insensitive literal substring matching, multi-word adjacency caveat, the three match_mode outcomes (exact/none/all), and the meaning of `note` on no-match. This goes well beyond the structured hints and provides actionable expectations.

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?

The description is front-loaded with purpose and usage, then organized into Args and Returns sections. Every sentence contributes essential guidance, from matching semantics to return mode definitions. Despite length, it is efficient and free of redundancy.

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

Completeness5/5

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

The tool is simple (2 optional params) but the description covers the full workflow: when to call, how to pass the query, what schemas exist, and exactly what the response contains. It even addresses the no-match case and directs users to server instructions for chemical search, making it self-sufficient for an agent.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must fully compensate, and it does. For `query`, it explains keyword format, literal substring behavior, the single-keyword recommendation, and the phrase-matching pitfall. For `schema`, it enumerates known values with approximate attribute counts and describes what each catalog contains.

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?

The description opens with a specific verb-resource pair: 'Discover the RCSB PDB Search schema: attribute paths, value types, and operators.' It clearly identifies the tool as a catalog/lookup utility and distinguishes it from sibling search tools by instructing 'Call this FIRST' and referencing `rcsb_search_by_attribute` as the follow-up consumer.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance: 'Call this FIRST when a request resolves to a clear attribute and value but you don't know the exact path.' It also names the alternative tool (`rcsb_search_by_attribute`) and clarifies how the output feeds into other `rcsb_search_*` tools, plus separate guidance for the 'chemical' schema.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rcsb/rcsb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server