Skip to main content
Glama

assess_conformal_coating_application

Read-only

Evaluate a populated board’s conformal-coating application and process path to identify coating families, failure risks, evidence gaps, and review needs for safety-critical assemblies.

Instructions

Assess a populated board's conformal-coating and process path.

Free door, tiered answer — Free: Safety basics — always free · Pro: Safety basics · Business: Which coating family, how it fails, what you still must prove · Enterprise: + Named products tied to your controlled documents · governed review for safety-critical boards.

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": {
      "use_description": "<use_description>"
    },
    "name": "assess_conformal_coating_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
threatsNoNamed hazards such as humidity, condensation, salt, solvent, thermal cycling, vibration, or UV.
cure_methodNoExact-product cure route the facility can execute. Default: "".
sds_revisionNoControlled revision of that safety data. Default: "".
contact_stackNoMaterials and functional interfaces the coating, masking, cleaner, cure, or rework route can touch.
exact_productNoOptional exact formulation/product candidate. Default: "".
render_packetNoAlso return ``protection_packet_markdown`` — a human-readable protection assessment packet (verdict, binding, candidates, blocks, gaps, plan, governance) built from this same response. The packet is advisory and not persisted; it is not an approval record. Default: false.
geometry_flagsNoShadowed regions, low stand-offs, sharp edges, dense areas, or other coverage/cure constraints.
contact_reviewsNoPer-interface status records. Each can name ``contact`` or ``interface_class`` plus ``status``, ``exact_evidence``, and ``keep_out``. ``status`` is one of "supported_within_scope", "supplier_declared", "conditional", "contradicted", "out_of_scope", "keep_out" or "unknown" (any other spelling is refused by name); ``exact_evidence`` and ``keep_out`` are booleans. Unreviewed critical interfaces fail closed.
electrical_roleNoThe coating's electrical role: "environmental" for functional protection only, or "safety_insulation", "spacing_credit" or "high_voltage" when that credit is being requested (those escalate to governed review). Omitted or "unknown" prevents candidate ranking. Default: "".
regulated_scopeNoExplicit regulated or customer-governed scope. Default: false.
rework_requiredNoWhether service, removal, or repair is expected. Default: false.
shadow_geometryNoWhether the cure/application route has shadowed zones. Default: false.
use_descriptionYesMission, board context, and desired protection.
candidate_familyNoOptional family to screen, not approve. Default: "".
compliance_claimNoWhether the requested conclusion claims compliance. Default: false.
configuration_idNoOptional caller-supplied assembly/configuration identifier. It is not authoritative unless replaced by ``evidence_case_id``. Default: "".
evidence_case_idNoKiln-created configuration evidence case. When supplied, Kiln resolves its design-version identity and staleness rather than trusting ``configuration_id`` / ``configuration_revision`` strings. Default: "".
high_consequenceNoExplicit high-consequence application flag. Default: false.
isocyanate_statusNo``not_applicable`` or ``controls_reviewed`` when defensible; unknown blocks a named urethane route. Default: "unknown".
application_methodNoSpray, selective, dip, brush, deposition, etc. Default: "".
chemical_exposuresNoExact fluids/exposures when chemical resistance is part of the mission.
must_protect_zonesNoBoard zones that need a defensible protection state.
coverage_inspectionNoWhether named-zone coverage/cure inspection exists. Default: false.
cleanliness_evidenceNoWhether cleaning, residue, drying, and handling evidence exists for the actual process. Default: false.
exact_product_familyNoFamily asserted for the exact product. Default: "".
governance_requestedNoAlso return advisory change-review, evidence and approval prompts for this assembly. Default: false.
keep_outs_documentedNoWhether must-remain-uncoated zones are controlled. Default: false.
process_capabilitiesNoFacility/application/inspection capabilities.
current_sds_availableNoWhether the current safety data exists. Default: false.
supplier_data_currentNoWhether current evidence was actually checked. Default: false.
configuration_revisionNoOptional caller-supplied assembly/configuration revision. It is not authoritative unless replaced by a Kiln evidence case. Default: "".
exact_product_revisionNoControlled supplier-document revision. Default: "".
rework_plan_documentedNoWhether restoration/reinspection is controlled. Default: false.
secondary_cure_verifiedNoWhether the exact secondary-cure path is evidenced in those shadowed zones. Default: false.
spray_controls_availableNoFacility controls review for spray application. Default: false.
unknown_critical_contactsNoContacts whose exact material or functional compatibility remains unknown.
solvent_controls_availableNoFacility controls review for solvent routes. Default: false.
safety_document_revision_idNoOptional controlled safety-data-sheet revision attached to the same case. Caller booleans cannot override its status. Default: "".
product_document_revision_idNoControlled technical-data-sheet revision attached to ``evidence_case_id``. Required with a controlled case. Default: "".
exact_product_family_verifiedNoWhether current evidence verifies that family identity. This never verifies compatibility. Default: false.
uv_equipment_protocol_availableNoMatched UV equipment, operating controls, and product-specific cure protocol are available. Default: false.
chemical_exposure_details_completeNoWhether concentration, temperature, contact mode, and duration are supplied for each fluid. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed42 schema fields changedv1.5.1
    • changedInput schema / properties / application_method / description
      Previous value: -"Default: \"\"."New value: +"Spray, selective, dip, brush, deposition, etc. Default: \"\"."
    • changedInput schema / properties / candidate_family / description
      Previous value: -"Default: \"\"."New value: +"Optional family to screen, not approve. Default: \"\"."
    • changedInput schema / properties / chemical_exposure_details_complete / description
      Previous value: -"Default: false."New value: +"Whether concentration, temperature, contact mode, and duration are supplied for each fluid. Default: false."
    • addedInput schema / properties / chemical_exposures / description
      Added value: +"Exact fluids/exposures when chemical resistance is part of the mission."
    • changedInput schema / properties / cleanliness_evidence / description
      Previous value: -"Default: false."New value: +"Whether cleaning, residue, drying, and handling evidence exists for the actual process. Default: false."
    • changedInput schema / properties / compliance_claim / description
      Previous value: -"Default: false."New value: +"Whether the requested conclusion claims compliance. Default: false."
    • changedInput schema / properties / configuration_id / description
      Previous value: -"Default: \"\"."New value: +"Optional caller-supplied assembly/configuration identifier. It is not authoritative unless replaced by ``evidence_case_id``. Default: \"\"."
    • changedInput schema / properties / configuration_revision / description
      Previous value: -"Default: \"\"."New value: +"Optional caller-supplied assembly/configuration revision. It is not authoritative unless replaced by a Kiln evidence case. Default: \"\"."
    • addedInput schema / properties / contact_reviews / description
      Added value: +"Per-interface status records. Each can name ``contact`` or ``interface_class`` plus ``status``, ``exact_evidence``, and ``keep_out``. ``status`` is one of \"supported_within_scope\", \"supplier_declared\", \"conditional\", \"contradicted\", \"out_of_scope\", \"keep_out\" or \"unknown\" (any other spelling is refused by name); ``exact_evidence`` and ``keep_out`` are booleans. Unreviewed critical interfaces fail closed."
    • addedInput schema / properties / contact_stack / description
      Added value: +"Materials and functional interfaces the coating, masking, cleaner, cure, or rework route can touch."
    • changedInput schema / properties / coverage_inspection / description
      Previous value: -"Default: false."New value: +"Whether named-zone coverage/cure inspection exists. Default: false."
    • changedInput schema / properties / cure_method / description
      Previous value: -"Default: \"\"."New value: +"Exact-product cure route the facility can execute. Default: \"\"."
    • changedInput schema / properties / current_sds_available / description
      Previous value: -"Default: false."New value: +"Whether the current safety data exists. Default: false."
    • changedInput schema / properties / electrical_role / description
      Previous value: -"Default: \"\"."New value: +"The coating's electrical role: \"environmental\" for functional protection only, or \"safety_insulation\", \"spacing_credit\" or \"high_voltage\" when that credit is being requested (those escalate to governed review). Omitted or \"unknown\" prevents candidate ranking. Default: \"\"."
    • changedInput schema / properties / evidence_case_id / description
      Previous value: -"Default: \"\"."New value: +"Kiln-created configuration evidence case. When supplied, Kiln resolves its design-version identity and staleness rather than trusting ``configuration_id`` / ``configuration_revision`` strings. Default: \"\"."
    • changedInput schema / properties / exact_product / description
      Previous value: -"Default: \"\"."New value: +"Optional exact formulation/product candidate. Default: \"\"."
    • changedInput schema / properties / exact_product_family / description
      Previous value: -"Default: \"\"."New value: +"Family asserted for the exact product. Default: \"\"."
    • changedInput schema / properties / exact_product_family_verified / description
      Previous value: -"Default: false."New value: +"Whether current evidence verifies that family identity. This never verifies compatibility. Default: false."
    • changedInput schema / properties / exact_product_revision / description
      Previous value: -"Default: \"\"."New value: +"Controlled supplier-document revision. Default: \"\"."
    • addedInput schema / properties / geometry_flags / description
      Added value: +"Shadowed regions, low stand-offs, sharp edges, dense areas, or other coverage/cure constraints."
    • changedInput schema / properties / governance_requested / description
      Previous value: -"Default: false."New value: +"Also return advisory change-review, evidence and approval prompts for this assembly. Default: false."
    • changedInput schema / properties / high_consequence / description
      Previous value: -"Default: false."New value: +"Explicit high-consequence application flag. Default: false."
    • changedInput schema / properties / isocyanate_status / description
      Previous value: -"Default: \"unknown\"."New value: +"``not_applicable`` or ``controls_reviewed`` when defensible; unknown blocks a named urethane route. Default: \"unknown\"."
    • changedInput schema / properties / keep_outs_documented / description
      Previous value: -"Default: false."New value: +"Whether must-remain-uncoated zones are controlled. Default: false."
    • addedInput schema / properties / must_protect_zones / description
      Added value: +"Board zones that need a defensible protection state."
    • addedInput schema / properties / process_capabilities / description
      Added value: +"Facility/application/inspection capabilities."
    • changedInput schema / properties / product_document_revision_id / description
      Previous value: -"Default: \"\"."New value: +"Controlled technical-data-sheet revision attached to ``evidence_case_id``. Required with a controlled case. Default: \"\"."
    • changedInput schema / properties / regulated_scope / description
      Previous value: -"Default: false."New value: +"Explicit regulated or customer-governed scope. Default: false."
    • changedInput schema / properties / render_packet / description
      Previous value: -"Default: false."New value: +"Also return ``protection_packet_markdown`` — a human-readable protection assessment packet (verdict, binding, candidates, blocks, gaps, plan, governance) built from this same response. The packet is advisory and not persisted; it is not an approval record. Default: false."
    • changedInput schema / properties / rework_plan_documented / description
      Previous value: -"Default: false."New value: +"Whether restoration/reinspection is controlled. Default: false."
    • changedInput schema / properties / rework_required / description
      Previous value: -"Default: false."New value: +"Whether service, removal, or repair is expected. Default: false."
    • changedInput schema / properties / safety_document_revision_id / description
      Previous value: -"Default: \"\"."New value: +"Optional controlled safety-data-sheet revision attached to the same case. Caller booleans cannot override its status. Default: \"\"."
    • changedInput schema / properties / sds_revision / description
      Previous value: -"Default: \"\"."New value: +"Controlled revision of that safety data. Default: \"\"."
    • changedInput schema / properties / secondary_cure_verified / description
      Previous value: -"Default: false."New value: +"Whether the exact secondary-cure path is evidenced in those shadowed zones. Default: false."
    • changedInput schema / properties / shadow_geometry / description
      Previous value: -"Default: false."New value: +"Whether the cure/application route has shadowed zones. Default: false."
    • changedInput schema / properties / solvent_controls_available / description
      Previous value: -"Default: false."New value: +"Facility controls review for solvent routes. Default: false."
    • changedInput schema / properties / spray_controls_available / description
      Previous value: -"Default: false."New value: +"Facility controls review for spray application. Default: false."
    • changedInput schema / properties / supplier_data_current / description
      Previous value: -"Default: false."New value: +"Whether current evidence was actually checked. Default: false."
    • addedInput schema / properties / threats / description
      Added value: +"Named hazards such as humidity, condensation, salt, solvent, thermal cycling, vibration, or UV."
    • addedInput schema / properties / unknown_critical_contacts / description
      Added value: +"Contacts whose exact material or functional compatibility remains unknown."
    • addedInput schema / properties / use_description / description
      Added value: +"Mission, board context, and desired protection."
    • changedInput schema / properties / uv_equipment_protocol_available / description
      Previous value: -"Default: false."New value: +"Matched UV equipment, operating controls, and product-specific cure protocol are available. Default: false."
  2. Addedv1.5.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already state readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds only 'governed review for safety-critical boards,' which hints at escalation but never explains it (what triggers it, what it returns). The tier breakdown is marketing rather than behavioral disclosure about the returned assessment.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is a clean, front-loaded statement of purpose. The second is a dense, punctuation-heavy tier ladder ('Free: ... · Pro: ... · Business: ... · Enterprise: ...') that consumes most of the word budget and reads as promotional copy rather than operative guidance.

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 42-parameter, high-stakes safety assessment with no output schema, the description is thin: it never describes the shape of the answer, what 'blocks' or 'gaps' mean, or how tier gating changes the response. The one useful signal is that Enterprise adds 'governed review,' implying the call can escalate.

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 100% and each of the 42 parameters carries a substantive description, so the schema does the heavy lifting and baseline 3 applies. The tool description adds nothing about parameters — not even the single required field, use_description, or how evidence_case_id supersedes configuration_id. With this many inputs, some prioritization would have helped.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb and resource: 'Assess a populated board's conformal-coating and process path.' But 'assess' stays abstract — it never says what the assessment produces (verdict, candidate list, gaps, blocks) or what a 'process path' evaluation means. The remaining text switches to tier/packaging language rather than sharpening the purpose.

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 guidance on when to call this versus alternatives, no prerequisites, and no exclusion conditions. The sibling tools include adjacent assessment tools (assess_bom_sourcing_risk, check_chemical_resistance, manage_protection_outcomes) yet none are named or contrasted. The tier list describes commercial access, not invocation conditions.

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

Deploy Server

Other Tools