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

io.github.chowdhurylab-studio/ipro-agent

ipro_positions

Propose design positions by selecting residues within a distance cutoff of a named partner molecule, so you can target an interface or pocket without listing residue numbers manually.

Instructions

Propose design positions from the structure: residues of the design molecule within a cutoff of a named partner, i.e. the interface or pocket. Use it when the user says 'the interface' instead of listing residue numbers.

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": {
      "spec": "<spec>"
    },
    "name": "ipro_positions"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNoname of the partner molecule to measure from
specYesPath to a spec YAML/JSON file, OR the spec's YAML content inline. Inline content is written to a temporary file first. Relative molecule paths inside a spec resolve against the spec file's own directory, so inline specs must use absolute structure paths.
cutoffNodistance cutoff in Angstroms (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It explains the conceptual operation but does not disclose whether the tool is read-only or mutating, what side effects occur, what permissions are needed, or what it returns; the schema mentions temporary-file handling for inline specs, but the description adds no such operational context.

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?

The description is compact and front-loads the core operation before the usage cue. It is efficient, though the interface/pocket phrasing repeats the same idea and could be tightened slightly.

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?

The tool has only three fully documented parameters and no output schema, so the description need not explain return values. However, with no annotations it should do more to cover operational behavior and result expectations; it is adequate for selecting the tool but incomplete for invoking it confidently.

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 input schema already documents all three parameters. The description reinforces the roles of the partner molecule and cutoff in interface/pocket selection, but adds no syntax, format, or edge-case detail beyond what the schema provides.

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?

The description states a specific verb and resource: proposing design positions as residues of the design molecule within a cutoff of a named partner, explicitly equated with the interface or pocket. This is clear, but it does not name or distinguish any sibling tools, so it falls short of a 5.

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 a clear usage scenario: use when the user refers to 'the interface' rather than listing residue numbers. It does not state when not to use it or name alternative tools, so the guidance is solid but not exhaustive.

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