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

io.github.chowdhurylab-studio/ipro-agent

ipro_inspect_structure

Inspect PDB/mmCIF structures to report chains, residue ranges, sequences, ligands, and waters, and resolve named residues to native identities with paste-ready spec lines before design specs.

Instructions

What is in a structure file: chains, residue counts and ranges, the one-letter sequence, ligands and waters -- and, for residues you name, the NATIVE identity plus a ready-to-paste spec line. Call this before writing a spec, every time. A user who says 'residues 18, 20, 38 and 40' has not said which chain, and a residue number that resolves to the wrong chain silently designs a different residue. It needs no PyMOL and no network.

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": {
      "structure": "<structure>"
    },
    "name": "ipro_inspect_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainsNorestrict the report to these chains
positionsNoresidues to report the native identity of, e.g. ["18", "A20", "1:115"]
structureYespath to a PDB or mmCIF file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it states the tool needs no PyMOL and no network, implying a pure local read with no side effects, and it discloses the report's contents and the silent-wrong-chain risk. It stops short of covering error behavior on a missing/unparseable file or any size limits on large mmCIF inputs.

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?

Content is front-loaded: the report inventory comes first, then the usage rule, then the rationale. The 'Call this before writing a spec, every time' sentence plus the follow-on example restates the same imperative twice, which is emphatic but slightly redundant.

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?

There is no output schema, so the description must describe return values, and it does so by listing each section of the report. For a three-parameter, read-only inspection tool that is nearly sufficient; only the concrete shape of the output and failure modes are left implicit.

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%, so the schema already documents all three parameters and the baseline is 3. The description adds some meaning — that 'positions' yields NATIVE identity and a pasteable spec line, and why 'chains' matters for disambiguating residue numbers — but it does not explain the accepted position syntax ('A20', '1:115') beyond the schema's own example.

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 names the resource (a structure file) and enumerates exactly what the report contains: chains, residue counts and ranges, one-letter sequence, ligands, waters, and native identity plus a spec line for named residues. That inventory lets an agent distinguish it from ipro_fetch_structure or ipro_positions without opening any schema.

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

Usage Guidelines5/5

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

It gives an explicit, unconditional prescription: 'Call this before writing a spec, every time,' and then justifies it with the concrete failure mode of a residue number resolving to the wrong chain. No alternatives are named, but the when-to-use rule is unambiguous and mandatory rather than optional.

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