Skip to main content
Glama
dcfg-mcp

dcfg-mcp

classify_corrosion_coupon

Classifies copper and silver corrosion coupon results per ANSI/ISA-71.04 by normalizing film thickness to 30 days and reporting the worse room class (G1/G2/G3/GX).

Instructions

Classify a corrosion coupon result under ANSI/ISA-71.04-2013 (G1/G2/G3/GX).

Normalises the measured film thickness to 30 days (R30 = X * 30 / T), classifies copper and silver separately, and reports the room class as the worse of the two. A copper-only result cannot prove G1. Field blanks are reported but never subtracted.

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": {
      "copper_film_angstrom": "<copper_film_angstrom>",
      "exposure_days": "<exposure_days>"
    },
    "name": "classify_corrosion_coupon"
  }
}

Input Schema

NameRequiredDescriptionDefault
exposure_daysYes
copper_film_angstromYes
silver_film_angstromNo
copper_blank_angstromNo
silver_blank_angstromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the normalization formula (R30 = X * 30 / T), the aggregation rule (class reports the worse of copper and silver), the copper-only caveat, and the blank-handling policy (reported but never subtracted). Gaps remain around invalid input handling (e.g., zero exposure days) and whether classification is purely computed or reads stored data.

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?

Four short sentences, purpose front-loaded, then the math, then the aggregation rule, then the two substantive caveats. Every sentence adds information an agent cannot get from the schema, and nothing is repeated from structured fields.

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?

For a 5-parameter, purely computational tool with no annotations and no output schema, the description covers inputs and the classification rule well but says nothing about the return shape (fields per metal, R30 values, blank reporting) or error behavior. An agent knows what the tool computes but not what it receives back.

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?

Schema description coverage is 0%, so the description must compensate, and it does: the R30 formula gives meaning to the exposure and film-thickness inputs, and the blank sentence explains the role of copper_blank_angstrom and silver_blank_angstrom as reported-but-not-subtracted. It never explicitly states that silver_film_angstrom is optional or that exposure_days must be positive, leaving minor gaps.

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?

Names a specific verb+resource ("Classify a corrosion coupon result") and pins the exact standard and output classes (ANSI/ISA-71.04-2013, G1/G2/G3/GX). Sibling tools (classify_procedure, liquid_loop_hydraulics) are unrelated domains, so no explicit disambiguation is needed, but the description never distinguishes itself by name.

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 rather than stated: an agent can infer this is for corrosion coupon measurements with copper and optional silver film thickness. There is useful domain guidance ("a copper-only result cannot prove G1") that shapes interpretation, but no explicit when-to-use or when-not-to-use framing against any alternative.

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