Skip to main content
Glama

Alphafold Prediction

alphafold_prediction
Read-onlyIdempotent

Full prediction metadata + structure file URLs (PDB, CIF, PAE).

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": {
      "qualifier": "P00533"
    },
    "name": "alphafold_prediction"
  }
}

Input Schema

NameRequiredDescriptionDefault
qualifierYesUniProt accession, e.g. "P00533"

Output Schema

NameRequiredDescriptionDefault
countNo
itemsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds the useful detail that results include downloadable structure file URLs (PDB, CIF, PAE), but says nothing about size/latency or what happens for an unpublished or invalid accession.

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?

A single short sentence with zero filler, front-loading the most important fact (full metadata plus file URLs) and then qualifying it with the concrete formats. Nothing is wasted or buried.

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

Completeness3/5

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

With an output schema present, the description needn't explain return values, and it correctly signals the artifact set. However, for a tool whose only real decision point is 'full vs summary', the missing routing guidance leaves the definition adequate but incomplete.

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?

Schema coverage is 100% and the single 'qualifier' parameter already documents itself as a UniProt accession with an example, so the description adds nothing on parameter meaning. Baseline 3 applies when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (Alphafold prediction metadata and structure files) and enumerates the returned artifact types (PDB, CIF, PAE). The word 'Full' implicitly contrasts with the sibling alphafold_summary, but the sibling is never named, so differentiation is left to inference.

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?

The description contains no when-to-use guidance, no prerequisites (e.g. a valid UniProt accession must exist), and never names alphafold_summary as the lighter alternative. An agent must guess whether it needs full structure URLs or just a summary.

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.