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

io.github.chowdhurylab-studio/ipro-agent

ipro_goals

Lists supported protein redesign goals and their source papers, helping you select the right objective before drafting a specification.

Instructions

The design objectives this tool can express (bind_tighter, switch_specificity, reshape_channel, improve_catalysis, stabilize), each with the paper it comes from. Use it to pick a goal before writing a spec.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 and no output schema, the description carries the burden alone. It discloses that the response pairs each goal with the paper it comes from, and the zero-parameter signature makes the read-only nature obvious, but it says nothing about result shape, ordering, or whether the values map to fields usable in a later spec write.

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 first enumerates the returned values, the second states the workflow timing. The parenthetical list earns its space because each goal name is a value the agent will later use.

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 trivial zero-parameter enumeration tool this is close to complete: it says what comes back, with what provenance, and when to call it. The only real gap is how the returned goal names connect to the sibling tools that consume them (e.g., spec writing or ipro_run).

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 the baseline is 4; there is nothing for the description to clarify beyond confirming the call needs no input.

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 concretely (design objectives / goals) and enumerates the five values it returns with their provenance. It lacks an explicit verb like 'list' but the intent is unmistakable and clearly distinct from action-oriented siblings such as ipro_run or ipro_validate.

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 gives explicit timing guidance: 'Use it to pick a goal before writing a spec,' which positions the call at the start of a workflow. It does not name a specific alternative or a when-not condition, so it stops 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.