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

io.github.chowdhurylab-studio/ipro-agent

ipro_score

Measure interaction energies and goal scores for a structure without running a design, providing a wild-type baseline or reference interaction values for constrained redesign.

Instructions

Measure a structure without designing anything: interaction energies per partner, the goal's score and its components, plus the run mode and notes. Use it for a wild-type baseline, or to get goal_options.reference_interaction before a constrained run.

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

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does clarify that the tool is non-mutating ('without designing anything') and lists the reported outputs, which is meaningful since there is no output schema. It does not disclose prerequisites (e.g., whether setup/validate must run first), cost/runtime, or the temp-file write side effect noted only in the schema.

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?

Two compact sentences with the core purpose and the anti-confusion clause front-loaded, followed by the output inventory and use cases. No redundant or filler wording.

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?

For a one-parameter measurement tool with no output schema and no annotations, the description covers what is returned and when to reach for it. It leaves gaps around execution preconditions and cost, which matter for a tool that presumably runs a full evaluation run.

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?

Only one parameter with 100% schema coverage, so the schema already explains the path-or-inline spec and the relative-path resolution rule; a baseline 3 applies. The description adds a small amount by naming goal_options.reference_interaction as something the spec produces, but it adds no new syntax or format detail for the spec argument itself.

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?

States a specific verb and resource ('Measure a structure') and immediately scopes it against the design-oriented siblings with 'without designing anything.' It also enumerates what is produced (per-partner interaction energies, goal score and components, run mode, notes), so an agent can tell this apart from ipro_run/ipro_milp 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 Guidelines4/5

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

Gives two concrete usage contexts: a wild-type baseline, or retrieving goal_options.reference_interaction before a constrained run. That is real when-to-use guidance. The exclusion is only implied by 'without designing anything' rather than stated as an explicit when-not, keeping it below a 5.

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