Skip to main content
Glama
PDBeurope

PDBe MCP Servers

Official
by PDBeurope

get_key_validation_stats_api_validation_key_validation_stats

Read-only

Retrieve a validation summary of geometric and electron-density metrics for a PDB entry, including outlier counts, percentages, and RMSZ values per category.

Instructions

Provides a validation summary listing key geometric and electron-density–based metrics. For each category (e.g., bonds, angles, RNA suite, Ramachandran, sidechains, RSRZ), the report includes: - number of residues/instances checked - number of outliers - percent outliers - and, where applicable, RMSZ values. Categories with no relevant residues return null percentages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pdb_idYes4-character PDB id code. title: Pdb Id description: 4-character PDB id code.
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds context about the summary content but no additional behavioral traits (e.g., auth, rate limits).

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?

Concise, front-loaded purpose, with structured list of metrics and special case for null percentages. Every sentence adds value with no redundancy.

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?

Details output per-category metrics (counts, outliers, percent, RMSZ) and handles null cases. No output schema, but description compensates well. Lacks top-level structure specification.

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

Parameters3/5

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

Input schema has 100% coverage for the single parameter pdb_id, which is adequately documented. The description does not add further semantic meaning to the parameter beyond the schema.

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 provides a validation summary listing geometric and electron-density metrics, with specific categories and output fields. This distinguishes it from siblings like get_outliers (list of outliers) and get_summary_quality_scores (likely a different summary).

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 explicit guidance on when to use this tool versus alternatives. The description does not mention conditions for use or when to prefer other validation tools among the sibling list.

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/PDBeurope/PDBe-MCP-Servers'

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