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

io.github.chowdhurylab-studio/ipro-agent

ipro_doctor

Verify installed backends and run capabilities before protein redesign, returning can_run, can_design, degraded backends, and the resolved mode to report.

Instructions

What is installed and what a run can therefore do. Call this FIRST: it returns can_run, can_design and the degraded backend list, and the resolved mode must be reported with any design.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully reveals the three key return fields and a compliance rule about reporting resolved mode, but says nothing about side effects, whether the call is read-only, or whether it is expensive/slow to invoke — meaningful gaps for a preflight tool with zero annotation coverage.

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 with no filler, and the imperative 'Call this FIRST' is front-loaded after a single framing clause. The first sentence is a fragment that leans on the second to become concrete, which costs a little immediate clarity but no wasted words.

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?

With no output schema and no annotations, the description must cover return values, and it does name can_run, can_design, degraded backends and resolved mode. It does not explain what values those fields take or how a degraded backend should change downstream behavior, leaving a modest gap for a zero-param diagnostic tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is no parameter semantics to disambiguate; the baseline for a zero-param schema applies. The description correctly spends no words on inputs and instead spends them on outputs, which is the right allocation.

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 definition states a concrete capability probe: it reports what is installed and what a run can therefore do, naming the outputs (can_run, can_design, degraded backend list). That is specific enough to separate it from siblings like ipro_run, ipro_status or ipro_validate, though the opening sentence is phrased abstractly before the concrete field names arrive.

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?

'Call this FIRST' gives an explicit ordering instruction that an agent can act on, and the downstream obligation ('the resolved mode must be reported with any design') tells the caller what to do with the result. It never names an alternative to use instead or states conditions under which this call can be skipped, so it stops short of 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.