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

io.github.chowdhurylab-studio/ipro-agent

ipro_validate

Validate a protein design spec before running it: parse the file, resolve positions against its structure, and report design-space size plus any problems found.

Instructions

Check a design spec without spending any CPU: parses it, resolves positions against the structure, reports the design-space size and every problem found. Always do this before ipro_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_validate"
  }
}

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

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 meaningful work: it discloses the cost profile ('without spending any CPU'), the internal steps (parsing, position resolution), and the return content (design-space size and every problem found) — notable since there is no output schema. It does not say whether the tool has any persistent side effects or whether problems are returned as data versus raised as errors.

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 sentences with zero filler: the first explains what the check does and why it is cheap, the second gives the ordering constraint. Key information (cost, output) comes before the directive, so it reads well front-to-back.

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 one-parameter, non-mutating validation tool with no output schema and no annotations, the description covers purpose, cost, output content, and workflow position. The remaining gap is error-mode behavior — what an agent should expect when problems are found — which keeps it from being fully complete.

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?

There is a single parameter with 100% schema description coverage, including the inline-versus-path behavior and relative-path resolution rule, so the schema already does the heavy lifting. The description adds nothing about the spec format or the path/inline tradeoff, so baseline 3 applies.

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 ('Check a design spec') and immediately unpacks what checking means: parses, resolves positions against the structure, reports design-space size and problems. It also names the sibling it precedes (ipro_run), so an agent can place it in the workflow 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?

'Always do this before ipro_run' is an explicit, actionable sequencing rule, which is the main alternative an agent would consider. It stops short of saying when validation can be skipped (e.g. after a trivial spec edit) or what to do if validation reports problems, so it is clear context rather than full when/when-not guidance.

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