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

io.github.chowdhurylab-studio/ipro-agent

ipro_status

Monitor protein design runs with bounded progress—iterations, accepted counts, best score and mutations, mode, and notes—so you can poll safely without reading growing iteration logs.

Instructions

Progress of a run: iterations, how many were ACCEPTED, the best score and mutations, the mode and the notes. Cheap and bounded in size however long the run has gone on, so it is safe to poll. Never read iterations.jsonl directly -- it grows without limit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ipro_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idNoor just the id ipro_run returned
run_dirNothe run directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 delivers the key traits: the response is cheap and bounded in size no matter how long the run has gone on, making polling safe. That is genuine cost/performance disclosure an agent could not get from the schema. It stops short of describing error behavior when the run is unknown or what happens if both run_id and run_dir are omitted.

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, zero filler. The returned content is front-loaded, the polling guidance follows, and the file-system warning closes it out as an actionable caveat.

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 and no annotations, so the description wisely enumerates the returned fields itself and adds a size/cost guarantee. For a two-parameter, zero-required read tool this covers nearly everything an agent needs, with only failure modes left unstated.

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 run_id and run_dir are already documented in the schema, establishing the baseline of 3. The description adds no further meaning about how the two identifiers relate or which one is preferred when both are supplied.

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 names the resource (a run's progress) and enumerates exactly what is reported: iterations, accepted count, best score and mutations, mode, notes. That is far more specific than the bare name 'status'. It does not, however, distinguish itself from near-siblings such as ipro_iterations or ipro_result, so an agent must still infer which summarizer to pick.

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

Usage Guidelines3/5

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

'Safe to poll' implies the intended use case (repeated checks while a run is in flight) and the warning against reading iterations.jsonl directly steers away from a raw-file alternative. But that warning targets a file, not a sibling tool, and there is no statement of when to prefer ipro_result, ipro_iterations, or ipro_runs instead.

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