Skip to main content
Glama

CovaSyn Chemistry Tools

covadoe_residual_diagnostics

Residual diagnostics: normality (Shapiro-Wilk), Cook's distance, leverage, and layout_check: residuals vs run order (trend, Durbin-Watson) and plate position.

`factor_info` (list of {name, factor_type:"categorical", levels:[...]}) dummy-codes
categorical factors. `plate_layout` maps roles (well, row, column, plate, run_order,
internal_standard) to columns; a `run_order`/`RunOrder` column is used automatically.

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

Input Schema

NameRequiredDescriptionDefault
dataYes
api_keyNo
responseYes
factor_infoNo
model_termsNolinear
plate_layoutNo
factor_columnsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.9/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 behavioral burden. It does disclose meaningful mechanics beyond the schema: categorical factors are dummy-coded via factor_info, plate_layout maps roles to columns, and a run_order/RunOrder column is picked up automatically. However, it never says whether the tool fits a model internally from data/response/model_terms, what happens with missing or non-numeric columns, or whether api_key is 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?

The text is compact and front-loads the computed diagnostics before the column-mapping details, with no filler sentences. The dense backtick-heavy phrasing and the abrupt 'layout_check:' fragment slightly hurt readability but nothing is redundant.

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?

An output schema exists, so return values need not be explained, but for a 7-parameter tool with zero schema coverage and no annotations the description is under-specified. It omits what model_terms accepts, how data/response must be shaped, and the role of api_key, which an agent needs in order to invoke the tool correctly.

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% across 7 parameters, and the description only explains factor_info, plate_layout, and the implicit run_order handling. The required data and response parameters, api_key, factor_columns, and the model_terms parameter (default 'linear') receive no explanation at all, leaving nearly half the surface undocumented.

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 concrete outputs it computes (Shapiro-Wilk normality, Cook's distance, leverage, residuals vs run order with trend and Durbin-Watson, plate position), so an agent knows exactly what the tool produces. It does not distinguish itself from sibling DOE tools such as covadoe_analyze or covadoe_fit_rsm, leaving the agent to infer that this is the post-fit diagnostic step.

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?

There is no explicit statement of when to use this versus covadoe_analyze, covadoe_model_selection, or covadoe_fit_rsm, and no preconditions (e.g., that a model must already be fit or that data/response must correspond to an analyzed design). Usage is only implied by the word 'diagnostics'.

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.