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

io.github.chowdhurylab-studio/ipro-agent

ipro_milp

Writes the rotamer-selection integer program to a CPLEX LP file and reports its size, so you can verify stated constraints before starting a long design run.

Instructions

Emit the rotamer-selection integer program as a CPLEX LP file and report its size. Use it to prove to a user that their stated constraints really are in the program before a long 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_milp"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNowhere to write the LP file
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 provided, the description carries the full disclosure burden; it does make the key side effect clear (an LP file is written to disk) and frames the tool as a pre-flight inspection. However, it says nothing about error behavior for invalid specs, whether anything else is mutated, or whether the run is aborted or continued, leaving meaningful behavioral gaps for a write-producing tool.

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?

Two tight sentences: the first states what is produced, the second states why an agent would call it, with the purpose front-loaded. Nothing is redundant, though the second sentence could be marginally tighter.

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 two-parameter, no-output-schema tool this is largely complete: the artifact, its purpose, and the pre-run timing are all covered. The one soft spot is 'report its size' — with no output schema, the description doesn't indicate what size metrics are reported or where the agent should look for them.

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 both `out` and `spec` are already fully documented in the schema, and the description adds no syntax or format detail beyond that. The baseline of 3 applies when the schema does the parameter-level work.

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 gives a specific verb and resource ('Emit the rotamer-selection integer program as a CPLEX LP file') plus the secondary effect ('report its size'), which makes the output artifact and the diagnostic intent unmistakable. The closing phrase 'before a long run' implicitly distinguishes it from the execution-oriented siblings such as ipro_run.

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 states a clear context for use — proving to a user that their stated constraints are actually encoded in the program before committing to a long run — which tells an agent when this diagnostic is warranted. It does not name an explicit alternative (e.g., ipro_validate) or state when not to use it, so it falls short of full routing guidance.

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