Skip to main content
Glama
io.github.chowdhurylab-studio/ipro-agent

io.github.chowdhurylab-studio/ipro-agent

ipro_fetch_structure

Download PDB structures by four-character ID from RCSB, optionally writing a chain-reduced copy. Use it when a protein name or PDB entry is given instead of a file.

Instructions

Download a structure from the RCSB PDB by its four-character ID (e.g. 2OMF), optionally writing a copy reduced to one chain. This is the ONLY tool here that uses the network. Use it when the user names a protein or a PDB entry rather than giving you a file. Always check what you got with ipro_inspect_structure afterwards: resolution, missing residues and engineered mutations all change what a design means.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pdb_id": "<pdb_id>"
    },
    "name": "ipro_fetch_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNooutput path (default <ID>.pdb)
forceNooverwrite an existing file
chainsNoalso write a copy reduced to these chains; a design spec's residue numbers are per chain
pdb_idYese.g. 2OMF, 1CRN

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does useful work: it discloses the network dependency, optional chain-reduced output, and the importance of checking resolution, missing residues, and mutations afterward. It does not cover failure modes, rate limits, or exactly what is returned beyond the written file, which keeps it short of a 5.

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?

Three sentences are front-loaded with the core action, then the network-only distinction, then a critical follow-up check. Every sentence contributes actionable information with no wasted wording.

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?

For a download tool with no output schema, the description covers the main workflow and points to the necessary inspection step. It could say more about what is returned or how failures manifest, but it is complete enough to call correctly.

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 description coverage is 100%, so the schema already documents pdb_id, out, force, and chains. The description adds useful rationale for chain reduction by noting that design-spec residue numbers are per chain, but it does not add syntax or deeper meaning beyond that for the other parameters.

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 states a specific verb and resource: downloading a structure from the RCSB PDB by four-character ID, with an optional chain-reduced copy. It also distinguishes this tool from siblings by explicitly saying it is the only one that uses the network.

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

Usage Guidelines4/5

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

It gives clear when-to-use guidance: use this when the user names a protein or PDB entry rather than providing a file. It also directs the agent to follow up with ipro_inspect_structure, though it does not explicitly state when not to use this tool or name a competing alternative beyond the inspection step.

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