Skip to main content
Glama

CovaSyn Chemistry Tools

covadoe_analyze

Run ANOVA analysis on experimental results.

Returns OLS coefficients (coded + uncoded, with a plain-language model_equation_uncoded),
Type III ANOVA (+ Type I sequential SS under anova_type1), and significance. Blocking and
split-plot terms are picked up automatically from "Block"/"WholePlot" columns. Optional:
`factor_info` (list of {name, factor_type:"categorical", levels:[...]}) enables multi-df categorical
F-tests; `response_family` ("gaussian"|"binomial"|"poisson") fits a GLM for non-normal responses.

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": "<response>"
    },
    "name": "covadoe_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
api_keyNo
responseYes
factor_infoNo
model_termsNolinear
factor_columnsNo
response_familyNogaussian

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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. It does disclose genuine behavioral traits: automatic detection of blocking and split-plot terms from 'Block'/'WholePlot' columns, the returned statistics, and GLM fitting for non-normal families. It says nothing about the api_key parameter, error conditions, cost, or what happens if the auto-detected terms are undesired.

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?

Front-loaded with the core action and padded with no filler; the return values and optional behaviors are grouped logically. It is dense but each clause carries information, with only minor compression cost in readability.

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 7-parameter statistical tool with no annotations and no schema descriptions, the description covers purpose, outputs, and two of the five functional parameters. The unexplained model_terms and factor_columns parameters are the notable gap; the existence of an output schema relieves the need to detail return values further.

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%, so the description must compensate and does only partly. It gives the shape of factor_info and the allowed values of response_family, adding real meaning. But model_terms (default 'linear'), factor_columns, data, response, and api_key are never explained anywhere.

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?

States a specific verb and resource: 'Run ANOVA analysis on experimental results', elaborated with what is returned (OLS coefficients, Type III ANOVA, significance). This is enough for an agent to distinguish it from modeling siblings such as covadoe_fit_rsm or covadoe_canonical_analysis, though those alternatives are never named.

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?

Offers implied guidance via the 'Optional:' markers – factor_info for multi-df categorical F-tests, response_family for non-normal responses – which tells the agent when to supply those parameters. However, there is no statement of when to choose this tool over sibling analysis tools, no prerequisites, and no exclusions.

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.