Skip to main content
Glama

search_pdb_entity

Search for PDB entries in Protein Data Bank, Chemical Component Dictionary, or BIRD database using keywords. Returns results including title, authors, and citation metadata.

Instructions

Search for PDBj entry information by keywords.

Args: db (str): The database to search in. Allowed values are: - "pdb" (Protein Data Bank, protein structures) - "cc" (Chemical Component Dictionary, chemical components or small molecules in PDB) - "prd" (BIRD, Biologically Interesting Reference Molecule Dictionary, mostly peptides). query (str): Query string, any keywords that can be used to search for PDB entries. Accepts aliases: search, term, keyword, keywords, search_term, name. limit (int): The maximum number of results to return. Default is 20. Must be in [0, 500].

Note: The PDBj search hits multiple fields (title, authors, keywords, citation metadata), not just the title. An entry can appear even if its title does not contain the query. Always verify relevance against the returned name/title before relying on a hit.

Returns: str: A JSON-formatted string containing the search results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dbYes
queryNo
limitNo
searchNo
termNo
keywordNo
keywordsNo
search_termNo
nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses that the search hits multiple fields (title, authors, keywords, etc.) and that entries may appear even if the title doesn't match, advising verification. With no annotations, this is valuable behavioral context.

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 structured with clear sections (Args, Note) and no fluff. Every sentence provides necessary information, making it efficient for an AI agent to parse.

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?

Given the presence of an output schema, the description adequately covers the tool's behavior, parameters, and a critical caveat about search relevance. It could mention pagination or result limits beyond the 'limit' parameter, but it's sufficient.

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?

The description explains the 'db' parameter with its enum values, 'query' with its aliases (search, term, etc.), and 'limit' with default and range. Since the schema has 0% coverage, this adds essential meaning.

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 clearly states the tool searches for PDBj entry information by keywords, specifying three databases (pdb, cc, prd). This distinguishes it from sibling tools which target other databases like ChEMBL or NCBI.

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

Usage Guidelines2/5

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

No guidance on when to use this tool over alternatives. While siblings are diverse, the description does not explain scenarios where this search is preferred or how it differs from other search tools.

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/dbcls/togomcp'

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