Skip to main content
Glama

CovaSyn Chemistry Tools

covadoe_suggest_design

Recommend a design type based on number of factors and goal.

Pass `n_categorical` (how many of the n_factors are categorical, e.g. solvent,
ligand, base): classical designs such as CCD cannot carry them.

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": {
      "n_factors": "<n_factors>"
    },
    "name": "covadoe_suggest_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoscreening
api_keyNo
n_factorsYes
n_categoricalNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / n_categorical
      Added value: +{
      +  "default": 0,
      +  "title": "N Categorical",
      +  "type": "integer"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description must carry the behavioral burden. It does disclose a genuine domain rule (classical designs like CCD cannot accommodate categorical factors), which is useful context, but it never states that the operation is read-only/advisory, what the response contains, or that api_key may be required.

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 short sentences, front-loaded with the core action and followed by the one non-obvious parameter caveat. Minimal waste, though the parenthetical example list could be trimmed slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation. However, for a tool whose whole value is choosing among many sibling design tools, the missing valid values for goal and the unaddressed api_key parameter leave real gaps for an agent deciding how to call it.

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 0% across 4 parameters, so the description has to compensate. It handles n_categorical well (explaining it as the subset of n_factors that are categorical, with solvent/ligand/base examples) and references n_factors, but leaves goal's allowed values unstated and never mentions api_key.

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 gives a specific verb and resource: 'Recommend a design type' driven by factor count and goal. That is distinguishable from do-er siblings like covadoe_create_design or covadoe_design_power, though it never names an alternative explicitly.

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?

Usage is implied: call this before choosing a design, presumably ahead of covadoe_create_design. There is no explicit when-to-use/when-not statement, no mention that this only advises rather than builds a design, and no guidance on prerequisites such as an API key.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.