Skip to main content
Glama

Alphafold Summary

alphafold_summary
Read-onlyIdempotent

Short summary for a prediction (organism, sequence, mean pLDDT).

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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
qualifierYes

Output Schema

NameRequiredDescriptionDefault
structuresNo
uniprot_entryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing beyond repeating the summary contents — no note on whether lookups are cached, what happens when the identifier is unknown, or what openWorld access implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, front-loaded, with zero filler. It is efficiently written, though the terseness borders on under-specification rather than being a stylistic flaw.

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?

An output schema exists, so return values need not be described, and annotations cover the safety traits. However, for a lookup keyed by a single unexplained required identifier, the description leaves the critical input ambiguous, which is the main remaining gap.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter is named only "qualifier", which is opaque; the examples (P00533, Q9Y5K6) hint at UniProt accessions but the description never says so. The description mentions organism and sequence as summary fields, not as accepted input, so it does not compensate for the coverage gap.

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

Purpose3/5

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

The phrase "Short summary for a prediction" names the resource (a prediction) and the fields returned (organism, sequence, mean pLDDT), so the general intent is graspable. But it is a noun phrase rather than a specific verb, and it never clarifies how it differs from the sibling alphafold_prediction — whether it is a lightweight read of an existing prediction or something else.

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?

There is no statement of when to call this versus alphafold_prediction or any other sibling, no prerequisites, and no exclusions. An agent must guess whether this returns metadata about an already-computed prediction or triggers anything.

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.