Skip to main content
Glama

CovaSyn Chemistry Tools

covadoe_optimize

Multi-response optimization (desirability, Pareto, weighted sum).

`factor_info` (list of {name, factor_type:"categorical", levels:[...]}) makes the
optimizer search over the levels of categorical factors instead of treating them as numbers.

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": {
      "data": "<data>",
      "response_specs": "<response_specs>"
    },
    "name": "covadoe_optimize"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
methodNodesirability
api_keyNo
factor_infoNo
factor_columnsNo
response_specsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / factor_info
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Factor Info"
      +}
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds useful behavior for factor_info: categorical factors are searched over their levels rather than treated as numbers. However, it omits prerequisites for data and response_specs, does not explain api_key/auth expectations, and gives no sense of what the optimization procedure produces beyond the separate output schema.

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?

The description is two sentences with no filler, front-loading the purpose and method names before focusing on the one non-obvious parameter behavior. Every sentence adds distinct value.

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

Completeness2/5

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

For a six-parameter optimization tool with no annotations, the description is too thin. The output schema covers return values, but the required data and response_specs parameters are undocumented, and method selection plus categorical-factor interaction are only partially addressed.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for the six parameters. It documents factor_info's shape and semantics in detail and implies valid method values, but data, response_specs, factor_columns, and api_key remain unexplained. The parameter information is therefore useful but far from sufficient.

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 states a specific operation, multi-response optimization, and names three methods (desirability, Pareto, weighted sum), so the agent can identify the core purpose. It does not distinguish this tool from the sibling covadoe_find_optimum, so it stops short of full sibling differentiation.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool instead of covadoe_find_optimum, covadoe_fit_rsm, covadoe_predict, or other DOE siblings. The three method names are listed, but there is no indication of when to choose desirability versus Pareto versus weighted sum.

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.