Skip to main content
Glama
Mesteriis

Plasticity MCP

plasticity_verify_single_fastener_strength

Verify single-fastener plate strength by re-reading exact native CAD faces, then calculating bearing, shear, and tensile failure modes for an in-plane load.

Instructions

Re-read exact opposed native faces of one rectangular through-hole plate, replace all caller geometry, calculate three plate failure modes and persist a CAD-bound report. It does not mutate CAD. Search accessible primary product/material sources before asking the user for known facts. Before requesting missing print-material data, call plasticity_plan_single_material_strength_tests for the selected method and exact one-material process. Use its measurement matrix to ask only for evidence needed by that route; explain why the measurements matter and never invent coupon values or allowables. A DCB task may contain an explicitly labeled generic-PLA literature geometry as a starting reference only; do not present it as a Creality property, normative specimen size, or sample-count requirement, and require checking the selected process, fixture and method. Keep the confirmed road/build axes and same-material layer-interface assumptions explicit. For Creality PLA literature references, read plasticity://strength/interlayer-literature-baseline. It contains separate CR-PLA and Hyper PLA records plus generic-PLA Z-tension/DCB context; do not merge product families or transfer values across SKUs. It is a screening reference only: do not register literature values as physical coupons or interface tests, bind them to the user's exact K1C process, treat them as design allowables, or infer a traction-separation curve from fracture energy. Manufacturer-mirror discrepancies and non-matching printer/process tests must remain visible; ask for exact-process physical tests before a calibrated cohesive result. When the user provides raw direct-tension machine CSV, call plasticity_import_interface_tensile_csv first with explicit specimen-ID/force headers, delimiter, decimal separator, force unit and sign, measured net area and observed failure location for every coupon. Review its hashed peak-force preview; the importer does not filter or correct machine data, register a test, or derive DCB/ENF/MMB curves. For directly loaded specimens supplied in another format, record every sample's measured peak force, net cross-section, observed failure location and SHA-256/source locator, then call plasticity_calculate_interface_specimen_strengths; report force/area as nominal specimen stress. Include only confirmed interface failures in its summary statistics; show bulk/fixture failures individually and do not pool them with interface failures. Keep all statistics descriptive only. Do not call these local interface tractions or design allowables, and do not use them as a cohesive law. When a raw DCB force/displacement CSV is available, use plasticity_import_dcb_mode_i_energy_csv as a read-only preview. Map columns, units, signs and CSV formatting explicitly, then select the exact source record for every manually observed crack-growth point and enter that measured crack length; never let the importer filter traces, infer growth or select peak loads. It converts units only, preserves the source hash/record locators and calculates an exploratory MBT G_I(a) curve. Require the caller to establish machine-compliance-corrected load-point displacement and quasi-static linear-elastic behavior; attestations are not independent verification. Review selected rows, crack lengths, calculation and limitations against the physical log. If no CSV is available, plasticity_calculate_dcb_mode_i_energy accepts equivalent manually selected observations with traceable source hash/locators. This does not conform the test to ASTM D5528 (whose stated scope is unidirectional fiber composites), create a traction-separation law, or qualify CR-PLA. Never convert G_I into peak traction or strength without separate evidence. When raw ENF force/displacement CSV is available, use plasticity_import_enf_mode_ii_energy_csv as a read-only preview. Map columns, units, signs and CSV formatting; group calibration rows into each measured run/crack length, manually select only the initial-linear records, and manually select the observed initiation/peak record for the fracture run. The tool fits compliance from the selected rows, then the existing ENF calculator fits C against a^3 and returns exploratory G_IIc; it never searches for the linear range, crack growth or peak. Review each compliance fit, source hash/record locator, force/displacement correction and fixture log. If pre-reduced compliances are supplied, use plasticity_calculate_enf_mode_ii_energy directly. Neither path determines ASTM D7905 validity for printed PLA, registers physical evidence, builds an R-curve or yields a cohesive law. Keep the confirmed in-plane shear direction exact; do not merge ENF runs with differing direction just because their layer normals match. When the requested failure mode is layer separation, distinguish CR-PLA's physical tensile/infill study and the two-sample CR-PLA-associated vertical layer-adhesion screen from the Hyper PLA flat tensile/flexural study: observed flexural delamination is qualitative failure-mode evidence, not a measured interface law. The baseline also records an upright generic-PLA tensile coupon on a Creality Ender 3 Pro and a custom generic-PLA interface coupon/calibrated cohesive parameter; neither identifies the filament as Creality nor establishes a same-process cohesive calibration. For only a nominal normal-strength screen across the layers, use the focused layer-interface-normal-tension scope; require measured failure at the interface and do not use that peak as a cohesive law. Use layer-interface-mode-i for a Mode-I fracture response, layer-interface-mode-ii for exploratory ENF Mode-II initiation energy using a same-fixture compliance calibration, and layer-interface-mixed-mode only when the requested analysis needs DCB/ENF/MMB cohesive evidence. The focused ENF calculator fits the experimentally supplied compliance against crack length cubed and uses the initiation peak; it is not an R-curve, does not verify the physical fixture or raw compliance fit, and does not claim ASTM D7905 validity for printed PLA. Layerwise static FEA assumes perfectly bonded interfaces and cannot answer a delamination question. After reviewing an exploratory DCB energy preview against the physical test log, persist it only through plasticity_record_dcb_mode_i_energy_test with explicit confirmation that the measurements came from real physical tests. Retrieve a full record with plasticity_read_dcb_mode_i_energy_test and require exact process/interface-normal/protocol matching through plasticity_match_dcb_mode_i_energy_test before comparing runs. For ENF Mode-II energy, record reviewed measurements only through plasticity_record_enf_mode_ii_energy_test with the same physical-test confirmation; retrieve all calibration/fracture inputs with plasticity_read_enf_mode_ii_energy_test and exact-match process/interface-normal/in-plane-shear-axis/protocol using plasticity_match_enf_mode_ii_energy_test. Both immutable energy registries are separate from peak-strength and traction-separation records and are not consumed by cohesive FEA. For an exploratory mixed-mode initiation partition, use plasticity_calculate_mmb_mode_i_ii_energy only when measured MMB force and geometry, same-process flexural and orthotropic moduli, and material-axis mapping are available; require lever weight to be measured negligible or counterbalanced. This Reeder-Crews beam-theory estimate does not establish ASTM D6671 validity for printed PLA and does not replace full mixed-mode traction-separation curves or provide a cohesive law. For raw MMB force CSV, use plasticity_import_mmb_mode_i_ii_energy_csv only with manually selected initiation records and a physically observed criterion; it does not search traces for onset/peak. Record a preview only after reviewing the source and confirming the data are from physical tests; matching caller confirmation with plasticity_record_mmb_mode_i_ii_energy_test persists and server-recomputes this separate energy estimate. Use plasticity_match_mmb_mode_i_ii_energy_test only for the exact process, interface normal, shear axis and protocol; read the full evidence with plasticity_read_mmb_mode_i_ii_energy_test. This registry is not cohesive input or an FEA source. When force is unknown, ask what object is supported, how it is mounted and used. Record source, units and uncertainty; do not infer exact scale from an unscaled image. Ask at most one next-step question package per response, then wait for the user's answer. Include only facts needed to choose the next safe step; defer material, manufacturing, tolerances and detailed dimensions until they affect that decision. Re-evaluate after every answer and ask a focused follow-up only when it changes the method, required evidence or next action. If the user does not know, move to one useful contextual clue such as the supported object, use, environment or mounting; do not repeat a list of unknowns or guess. On a new bracket task, first ask compactly what it supports, its load/use and how it is mounted; defer section, material/process and displacement questions until that first answer narrows the load path and method. Choose a supported member method and report its unchecked components explicitly. For a flat rectangular panel, establish net pressure and the real condition of all four edges before choosing the simply-supported plate method. Do not infer edge support from appearance. For a straight prismatic rectangular member in centred axial compression, use the Euler column method only when effective-length factor K, elastic limit, compressive allowable, and the actual restraint condition are supported by evidence. Use the weakest section axis, require a negative force value for compression, and reject Euler results when its predicted critical stress exceeds the supplied elastic limit; do not guess K or treat the method as an inelastic, eccentric-load, local-buckling, or whole-part check. For an integral rectangular enclosure wall, inspect two opposed planar faces on the same Solid with plasticity_inspect_integral_rectangular_plate, then use plasticity_verify_integral_plate_strength to replace dimensions from exact native B-rep. The inspector accepts only rectangular faces whose outlines match or inset by one wall thickness on each side. It measures geometry only: establish the real support, pressure, material and edge conditions separately; never assume a box wall is simply supported. For section analysis, identify the critical plane and explain the load path that makes it critical. Use an existing planar face when it matches; otherwise inspect an arbitrary plane through the Solid. For one fastener carrying in-plane plate load, establish the load direction and separate bearing, shear and tensile allowables before calculating. Never substitute compressive strength for bearing strength. For a fastener group on a rectangular planar face, inspect exact hole centers and boundaries, then check center-to-edge distance, hole-edge clearance, pitch, ligament and every applicable head, washer, nut or driver envelope against explicitly sourced or user-approved criteria. A measured layout without criteria is not a pass, and a layout pass is not a strength pass. When checking the fastener member, establish its grade, tensile stress area, effective shear area at the actual plane, one or two shear planes, total axial tension including applicable preload, and actual shear load. Explain why the selected combined-load interaction is applicable before accepting it. For a tapped hole, nut, or threaded insert under axial load, establish the designation, pitch, actual engagement, fully formed engaged thread count, and configuration-matched allowable loads for internal-thread stripping, external-thread stripping, and fastener tension. Do not infer any capacity from nominal M size. A procured nut or insert requires a specified assembly allowable or dedicated test rather than an unqualified nominal shear-area calculation. For solver-backed static FEA, first use plasticity_match_material_coupon_data when a physically tested material record may match the print process. Only an unambiguous exact match for printer, material, profile hash, orientation, infill percentage and pattern, wall loops, top/bottom shell layers, nozzle temperature and measured slicer layer height can supply Young's modulus; pass the selected record ID/process and the exact recorded modulus so the server binds and validates it. If match is ambiguous because compatible partial records have no single consolidated record, ask the user for the confirmed count of unique physical specimens and call plasticity_combine_material_coupon_data with those exact record IDs; it preserves measured values and evidence without averaging. If records conflict, stop and ask the user which physical measurement applies. For an orthotropic print model, do not use a uniaxial coupon as a full tensor. When an immutable exact-process record contains the complete measured tensor and nu12, pass orthotropicMaterial.couponRecordId and process, plus materialCoupon with the same record ID; the MCP checks E1, nu12, every remaining constant, each evidence object and the confirmed global print axes, and rechecks the record when reading the saved report. Otherwise pass E2/E3, nu13/nu23, G12/G13/G23 with separate exact evidence, global material axes 1 and 2, and a user-confirmed or sourced global build direction; material axis 3 must align with that build direction and represents the homogeneous layer-normal response. This does not represent individual layers or prove adhesion. Model one material and one print process per analyzed part; do not combine material datasets or infer a multi-material print. When the selected exact-process coupon record contains a qualified Tsai-Wu dataset, pass its ID as orthotropicMaterial.tsaiWuQualificationRecordId along with the identical orthotropicMaterial.process; the server loads measured strengths, biaxial interaction data and source evidence, then verifies the axes. Do not copy or reconstruct criterion values by hand. If the exact-process match remains ambiguous after consolidation, ask the user to resolve conflicting measurements; never choose a record silently. The legacy youngsModulusMPa and poissonRatio fields are E1 and nu12. Ask the user to resolve the print-axis orientation if it is unknown; never infer it from a photo or CAD face. The server checks positive-definite compliance and rejects a von Mises allowable or coupon binding for this orthotropic model. Otherwise attach youngsModulusEvidence whose value exactly matches the modulus; measured/sourced evidence needs a URL, SHA-256 and locator. poissonRatioEvidence is always required and must exactly match the ratio. A physical coupon record may store measured nu12 with its exact process. If using its Tsai-Wu record-binding path, the server verifies the nu12 value and evidence against that record; otherwise supply the input evidence directly from a traceable source. Never infer nu12 from a generic plastic label. An assumed value must include its reason and stay explicitly scenario-only after discussing the assumption with the user. Optionally supply a directly measured or sourced, process-applicable factored von Mises design allowable using factoredVonMisesAllowableMPa, exact matching factoredVonMisesAllowableEvidence with URL, SHA-256 and locator, and factoredVonMisesAllowableBasis. It must already include the design factors. Never turn a generic tensile strength or raw coupon peak into a design allowable. The report will compare every sampled raw mesh peak with it as a diagnostic screen only: above means a sampled peak exceeds that supplied allowable; below does not prove strength. This never changes strengthPass or print approval. Confirm the actual restraints with the user. Legacy supportFaceIds fix all three global translations on each selected planar face; use explicit supportConditions only when the user has specified which global x/y/z translations are zero on each face. Each condition acts on all nodes of that face, is not a frictionless-contact or rotational support, and may leave rigid-body modes or create a singular system; do not infer it from a photo or face normal. Supports and loaded faces must not share mesh nodes. Every selected planar load face needs an explicit uniform traction and/or resultant force with its point of application and free moment. Use plasticity_analyze_static_fem only for one Solid with 1–8 explicit support conditions and load vectors grounded in a selected planar face. Use named loadCases for physically distinct scenarios such as weight, operating force and handling load; do not combine mutually exclusive scenarios. Each case has a separate solver result, and comparison proceeds only when the generated meshes are byte-identical. Set meshRefinementSteps to 1–3 for two to four mesh levels when a trend across successively halved element sizes is useful; the report classifies the sampled direction of raw maximum von Mises stress and observed displacement as increasing, decreasing, unchanged, non-monotonic or insufficient-levels. For more than four levels, run separate analyses against the same current CAD revision and call plasticity_compare_static_fem_refinement_reports; it merges only reports with matching loads, supports, material evidence, native geometry and byte-identical overlapping mesh results. Check the returned freshness before relying on it. Treat all trend labels and relative changes as diagnostic evidence only. Never call a mesh trend a pass or proof of convergence. Each result includes the raw maximum C3D4 integration-point stress element and its mesh-element centroid in millimetres; this is a mesh-bound locator, not an averaged stress field, a resolved critical-region boundary, or proof of a physical hotspot. Locations may move between refinement levels. The legacy top-level load fields still represent one case. The tool returns total and per-support reaction forces and moments, global force/moment equilibrium residuals and a named displacement axis for each case; per-support values are diagnostic resultants over each support node set. Re-read it with plasticity_static_fem_report; any CAD revision change makes it stale.

For layerwise static FEA, keep the single-material exact process consistent from measurement through solver input. Read the immutable profile hash, infill pattern, wall loops, top/bottom shell layers and measured layer height from workbench_manufacturing_profiles, then slice the intended model/orientation with the selected Creality K1C profile. Record actual specimen settings if per-object overrides differ from profile defaults; an unchanged profile hash does not erase those differences. Call workbench_slicer_layer_path_orientations in batches of up to 32 and combine layer-path results for every deposited layer, including the final deposited layer, into layerPathEvidence with identical job ID, profile hash, source-artifact hash and G-code hash. Layerwise static orientation is supported only for a complete linear or planar circular-arc direction result for every layer in stacks of 2–33 layers; do not fill missing or curved-path directions by inference. Confirm pathFrameMapping.slicerXDirectionGlobal in CAD global coordinates and explicitly confirm that the same exact-process coupon's material axis 1 represents the dominant deposited-road direction in roadAxisMapping. Call plasticity_plan_cohesive_layer_planes with the same profile hash and layer height, current CAD anchor at the first interlayer plane, confirmed CAD build direction, total layer count, and the full layer-path evidence/mappings; pass its returned plan as layerPlanePlan to plasticity_analyze_static_fem. When the slicer supplies actual interface heights, call workbench_slicer_interface_heights for every interface in this complete stack, set each interfaceOffsetsMm value to its depositionLayerZMm minus firstDepositionLayerZMm, and attach the matching job/profile/source/G-code hashes as depositionPathEvidence; this preserves first-layer and adaptive heights instead of assuming nominal uniform spacing. The static analyzer requires the plan to match the one measured orthotropic process and applies the same measured orthotropic tensor to each layer with its confirmed G-code-mapped frame. It assumes perfectly bonded layers and cannot assess delamination. Do not use static FEA to assess delamination; use the separate same-material cohesive route only when matching physical interface tests are available. Never infer layer directions, material identity or interlayer strength from a photo, generic material label or nominal slicer preset.

For orthotropic FEA, optionally supply all nine directly traceable, already factored X/Y/Z tensile and compressive plus XY/XZ/YZ shear limits in orthotropicMaterial.factoredAllowables, with separate exact-value evidence and an applicability/design-factor basis. Never substitute generic datasheet strength or an unqualified coupon peak. The returned componentwise maximum-stress screen uses local material-axis stress extrema and is diagnostic only; it assumes one homogeneous orthotropic continuum, does not model layer interfaces, delamination or different-material joints, and omits multiaxial interaction. Matched interlayer-test data can inform Z-tension and XZ/YZ-shear allowables but does not turn this into a cohesive-interface analysis. Never report this screen as verified layer adhesion, part strength or print approval. For an optional 3D Tsai-Wu first-failure screen in orthotropic linear FEA, require one exact single-material printer/material/profile hash, orientation, infill percentage and pattern, wall loops, top/bottom shell layers and nozzle-temperature identity in orthotropicMaterial.process. Prefer binding the unique exact-process qualification by its orthotropicMaterial.tsaiWuQualificationRecordId; the server loads its nine directly measured, un-factored X/Y/Z tensile/compressive and XY/XZ/YZ shear failure strengths, three normalized XY/XZ/YZ normal-interaction coefficients and evidence, then verifies material axes. Each strength test must attest its material-frame axis and mode (for example, x tension is material-1 tension; xy shear is material-1-2 shear); each interaction and its source dependencies must attest the corresponding biaxial plane. Legacy records without these direction attestations remain readable but cannot qualify a Tsai-Wu FEA. A complete inline orthotropicMaterial.tsaiWuCriterion remains supported when needed. Interactions must be derived from traceable biaxial tests. Ask the user for these records if missing; never copy generic datasheet values, assume the conventional interaction coefficient or infer it from uniaxial coupons. The normalized interaction matrix must be positive definite. The result reports local integration-point failure indices and proportional load factors to index one only. A load factor is not a design safety factor, and neither a sub-unity index nor a large load factor means the part passed. The model still represents one homogeneous material, not individual roads or delamination.

When actual test-coupon G-code is available, preserve its profile/source/G-code hashes, selected per-layer road summaries and explicitly user-confirmed slicer-to-global axes in depositionPathEvidence. This is test provenance only, not an adhesion measurement or solver input; never reconstruct road direction from nominal slicer settings.

When physical adhesion between printed layers of one material is relevant, use plasticity_record_material_interface_test only for caller-provided measured test results with the same exact printer/material/profile process on both sides, interface normal, test mode, load direction, fixture/specimen protocol hash and observed failure location. Normal-tension load direction must align with the interface normal; interface-shear load direction must lie in its plane; mixed-mode must contain both components. Store full compliance-corrected pure-mode curves as scalar separation/traction data and MMB curves as separate normal/tangential separation and traction components, with source SHA-256 and locator. Call plasticity_analyze_material_interface_test_curve to summarize measured work and mode mixity. When the user has a CSV of already processed physical fracture data, use plasticity_import_interface_fracture_csv for a read-only per-specimen preview; explicitly map the method, columns, units and CSV formatting, and attest that the values are already compliance-corrected physical traction-separation data. Never convert raw machine force-displacement data with this importer. Verify each source hash/record locator, specimen, fixture, exact print process and observed failure plane before separately recording any curve with plasticity_record_material_interface_test. For a CZM_TURON candidate fit, provide Mode-I DCB, Mode-II ENF and at least two MMB tests at distinct measured energy fractions; all ENF and MMB tests must use the same in-plane shear axis within one degree because this route has a single tangential cohesive law. The MCP requires those protocol identifiers in each testMethod and reports the pure-mode peaks plus fit residuals. Review residuals against test uncertainty. Do not invent ETA_BK. K is not identified by that fit and must not be silently guessed. Code_Aster CZM_TURON uses one normal and one tangential cohesive response, sharing tangential strength and fracture energy across both in-plane tangent directions; it cannot represent direction-dependent shear adhesion. Matching shear axes prevents mixing directional datasets but does not prove that the bond is isotropic. These outputs summarize physical evidence only; they are not qualified cohesive-law parameters, design allowables or a part FEA. Do not claim bond integrity from the homogeneous orthotropic FEA screen. Use plasticity_analyze_cohesive_interface only for a single-material printed part, with an exact-process coupon for that one bulk material, traceable Poisson ratio and a matching immutable same-material layer test. Dissimilar-material printed bonds are rejected before meshing and are outside this calculation scope. Mode-I analysis requires a full normal-tension DCB traction-separation curve with failure at the layer interface. Its modeILaw may explicitly select CZM_EXP_REG or CZM_LIN_REG; omitted input preserves the CZM_EXP_REG default. Both parameterize their softening law from measured peak traction and integrated fracture energy and do not fit the full measured curve shape. Review this choice against the measured curve and record the reason; do not infer it from part geometry. Read the returned solver.result.v3Interpretation: for CZM_EXP_REG, V3 is a damage variable in [0,1]; for CZM_LIN_REG, V3=2 means the cohesive element is completely broken, so do not present it as the same normalized damage fraction. By default it uses isotropic bulk elasticity with pinned Code_Aster 15.2. If useOrthotropicBulkProperties is explicitly enabled, Mode-I uses Code_Aster 17.4 and applies one measured homogeneous orthotropic tensor; when explicit layerwise mapping is enabled, each bulk layer uses its G-code-mapped frame while all layers share that same tensor. The mixed-mode Turon route additionally requires same-process-pair DCB, ENF and at least two MMB tests at distinct measured energy fractions, traceable K, and an explicit global displacement with both opening-normal and in-plane tangential components greater than one degree. The displacement's shear axis must match the common measured ENF/MMB shear axis within one degree; reject other directions because this solver law has one tangential response. All ENF and MMB tests must use the same in-plane shear axis within one degree. Supply 1..32 ordered parallel split planes for a same-material layer stack; their normals may be tilted in global coordinates, and the same measured layer law is repeated at every plane. This equivalent-interface assumption does not resolve individual roads or within-layer raster variation. Either route may accept useOrthotropicBulkProperties when the exact-process coupon contains measured E2/E3, nu13/nu23, G12/G13/G23 evidence and a confirmed or traceable global print frame. Check the exact-process coupon match is unambiguous and do not infer axes from a photo or CAD face. Confirm the tested material's side relative to the chosen split-plane normal; do not infer this from the body or face normals. The measured test direction must match the normal/shear mode; the support face lies below the first split plane and the loaded face above the last plane along the shared normal. The server derives peak traction, integrated fracture energy and displacement endpoint from exact tests, exports the selected current Solid, creates a conforming multi-region mesh with a cohesive element set at every requested plane, and aborts if the CAD revision changes. Review the mesh-resolution screen and perform refinement/sensitivity work as needed. Turon approximates measured curves using peak/area parameters and its K still needs sensitivity analysis. The bulk tensor remains one measured single-material continuum whose local frame may vary by mapped layer; repeated cohesive planes use the same measured, direction-independent interface law and do not resolve individual deposited roads, within-layer raster mixtures or direction-dependent adhesion. Use results only as raw solver responses; never report it as a part-strength verdict, qualified layer-adhesion value, print approval or design allowable. Before asking for a physical coupon record, obtain the selected immutable profile hash plus material.nozzleTemperatureC, slicer.layerHeightMm, slicer.nominalInfillPercent, slicer.sparseInfillPattern, slicer.wallLoops, slicer.topShellLayers, and slicer.bottomShellLayers from workbench_manufacturing_profiles when those settings are available. Carry the exact process values into the record; do not infer missing infill or substitute a generic profile. These are resolved profile defaults; sparse fill or shell settings may be overridden per object and must not be assumed when a modifier was used. If the coupon was printed with a different setting, first register/select the matching immutable process profile and hash. When layer positions should follow the actual print, record the measured profile hash and layer height in the physical interface-test and material-coupon process; layer height is part of exact process identity. After slicing, if the job reports a complete deposition-height schedule, call workbench_slicer_interface_heights for every selected interface index. Derive each offset as that interface’s depositionLayerZMm minus firstDepositionLayerZMm and pass the ordered values as interfaceOffsetsMm; this preserves first-layer and adaptive heights. Also pass the selected interface response plus its job/profile/source/G-code hashes, layer count and coordinate frame as depositionPathEvidence so the cohesive report retains the exact per-layer road-orientation observations. This evidence preserves the measured toolpath but does not qualify material properties. Use workbench_slicer_layer_path_orientations in batches of up to 32 to retrieve every layer direction (up to 33 total layers) when the user wants layerwise solver orientation. Confirm how slicer X maps into the CAD global frame and that the exact-process coupon axis 1 represents the dominant deposited-road direction; pass those confirmations as pathFrameMapping and roadAxisMapping. Combine complete responses, including the final deposited layer, as layerPathEvidence with shared job/profile/source/G-code hashes. Every layer must have complete linear or planar circular-arc coverage; do not treat unsupported arc/spline moves as complete. With explicit roadAxisMapping and useOrthotropicBulkProperties, Mode-I and Turon use one measured tensor with a separate local frame per layer. Without roadAxisMapping, frames remain candidates and do not affect solver response. This does not model multiple materials, layer-varying properties, within-layer raster mixtures or directional interface adhesion. Returned coordinates are in slicer build coordinates: map only relative offsets onto the confirmed CAD print axis, never copy absolute slicer Z into CAD. Otherwise the planner uses the nominal profile height. Call plasticity_plan_cohesive_layer_planes with that same profile hash and layer height, a point on the first interlayer plane after object placement, confirmed global build direction, total layer count and explicit interface indices. Copy both its plan and planes into layerPlanePlan and splitPlanes; analysis rejects legacy test records without a recorded layer height and any height that differs from the measured process profile. It also checks profile identity, plane coordinates, and (for orthotropic bulk) alignment with the coupon’s confirmed build direction. For up to 32 interfaces the planner requires the complete stack; for larger stacks it marks selected planes as incomplete, and omitted interfaces remain unanalyzed. Do not present selected-plane analysis as full-stack delamination resistance. If no validated placement/anchor is available, ask instead of inferring layer positions from an image or display mesh. Read maximumVonMisesElementSICN alongside each raw stress-peak locator to see the Gmsh SICN of that exact tetrahedron. Compare it with the mesh minimum only as local mesh-shape context; neither a high value nor separation from the minimum proves stress accuracy, a resolved hotspot, convergence, or strength. Read maximumPrincipalStressMPa and minimumPrincipalStressMPa as raw tensile/compressive principal extrema across sampled integration points, each with its own mesh locator. Their refinement trends and signed relative changes expose mesh sensitivity only; they are diagnostic and must never be compared with a von Mises allowable or reported as a pass without a criterion qualified for the selected failure mode. The public FEA tool measures the rank of all fixed global translations at the actual mapped mesh nodes and stops before CalculiX if they leave any of the six rigid-body translation/rotation modes unconstrained. A full rank of six is necessary to remove those rigid-body modes, but it does not establish physical support validity, elastic stability, or absence of local mechanisms. For a heat-set insert, use pullout and torque-out capacity only when the evidence matches the exact insert, host material, print profile, orientation, pocket and installation process. Ask for the worst-case demand on one insert; do not divide a group load evenly without a load-path model. For two or more fasteners under an in-plane load, establish every transfer-point coordinate, both force components, the point of application and any free moment. Use the elastic group method only after confirming a rigid attachment and identical in-plane fastener stiffness. Use each fastener’s own vector resultant for any member check. On a rectangular mounting face, call plasticity_check_fastener_group_layout with an explicit opposedFaceId to verify matching native perforated faces and exact plate thickness. This is geometry evidence only and does not establish a load path or capacity. plasticity_verify_fastener_group_plate_bearing compares each elastic per-fastener demand with a directly traceable, configuration-matched, already factored bearing allowable using exact measured thickness and hole diameter. It can additionally check a straight transverse net-tension section only when you provide the external tensile resultant separately, identify local X or Y as its axis, supply a distinct traceable factored tensile allowable, and confirm uniform membrane tension, centered through-thickness loading and a straight transverse failure path. Never substitute per-fastener demands for the external plate tension or infer that resultant from a sketch. Optionally use edgeShearOut with a separate traceable, factored shear allowable to check local two-plane tear-out for per-fastener vectors aligned to local X or Y; diagonal vectors and e/d below 1.5 are unsupported, while e/d below 2 remains conditional. Angled/staggered fracture paths, compression-side buckling, shared-ligament interaction, unsupported tear-out directions, bypass and complete-joint strength remain unchecked; even a within-allowable result is only a conditional local screen. If a physical multi-hole plate test is run, record the measured specimen, exact hole layout, print-process/profile, fixture, load axis, individual peak loads and observed failure modes with plasticity_record_fastener_group_test, then use plasticity_match_fastener_group_test to find only an exact configuration match. A test match is evidence only: it does not produce a design allowable or pass a different part or support setup. To add a test benchmark to the CAD-bound report, first confirm that the record's exact process and fixture/load path apply to the current part. Supply the selected immutable record ID, an independently evidenced dimensional equivalence tolerance, the exact process, safety factor, and explicit process/fixture confirmations; the server then checks every measured plate and hole dimension against the live B-rep. This comparison only checks factored external tensile demand against the lowest observed specimen peak. It is not a statistically reduced allowable, strength pass/fail, or proof for unobserved failure modes. Do not select a nearby test by appearance or silently assume fixture equivalence. The single-through-fastener plate method assumes one hole; never repeat it per hole and aggregate the results into a multi-hole plate or whole-joint pass. Calculate preliminary dimensions, then propose one logical CAD change in the chat. Execute only the accepted package or the current explicitly delegated task. Delegation ends when the task ends and is not restored after restart. Read actual native geometry and recalculate after manual edits or manufacturing changes. Workbench is optional. Unknown material properties cannot be converted into a pass by confidence language. For an end-to-end tongue-root scenario, use plasticity_calculate_tongue_root_strength_from_coupon_data or plasticity_verify_tongue_root_strength_from_coupon_data. They match the physical coupon record to the exact Workbench profile hash, printer, material, orientation, infill, nozzle temperature and measured slicer layer height, then copy only measured Young's/shear moduli and their evidence into the calculation. Supply separately sourced tensile/shear design allowables and explain their applicability; raw coupon strengths are never substituted for allowables. These tools keep material suitability unconfirmed and the result conditional. No-match or conflicting records return without a calculation. If no record exists, ask for the report and unresolved process details, and record it only after the user confirms the physical tests. The registry does not check test-standard compliance, derive statistical design values, or certify a part. Never substitute a generic filament label or slicer properties for coupon evidence. For axial rectangular or rectangular-cantilever scenarios with exact-process coupon data, use plasticity_calculate_rectangular_strength_from_coupon_data. It copies only measured Young's modulus and its evidence. Provide independent tensile design allowable evidence, plus an independent compressive allowable for a cantilever; state their applicability basis. Never map raw coupon tensile/compressive strengths into design allowables. These scenarios remain conditional with material suitability unconfirmed. Exact-process no-match or ambiguity returns without saving a calculation. Nominal section stress is not whole-part validation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalYes
kindYes
loadNYes
methodYes
bindingNo
evidenceYes
geometryYes
materialYes
assignmentsYes
assumptionsYes
safetyFactorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false with destructiveHint=false; the description adds the key clarification 'It does not mutate CAD' and that it 'persist[s] a CAD-bound report', resolving what the non-read-only behaviour actually is. It further discloses the one-hole assumption and that compressive strength must not be substituted for bearing, which are behavioural constraints beyond the annotations.

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 tool-specific content occupies roughly two sentences; the rest is thousands of words about DCB/ENF/MMB imports, Tsai-Wu, orthotropic FEA and cohesive laws that belong to sibling tools. The purpose is front-loaded, but the overwhelming majority of the text does not earn its place for this tool, making the relevant guidance hard to locate.

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?

With no output schema and a large nested input schema at zero description coverage, the description should explain the returned report's content and the parameter contract. It only says a 'CAD-bound report' with 'three plate failure modes' is persisted and remains conditional; the failure modes, units, evidence requirements and report fields are left unspecified.

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 11 parameters (10 required, nested geometry/material/evidence/assumptions objects), so the description must carry the load, but it does not map to any named field. It gestures at concepts (load direction, separate bearing/shear/tensile allowables, exact process identity, source SHA-256/locator) yet never explains what 'assignments', 'assumptions', 'sideClearancesMm', or the nested evidence 'status' values require.

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 opening sentence gives a specific verb and resource: 'Re-read exact opposed native faces of one rectangular through-hole plate, replace all caller geometry, calculate three plate failure modes and persist a CAD-bound report.' That lets an agent distinguish it from generic strength tools, but the three failure modes are never named and the description never contrasts it with the sibling 'plasticity_calculate_single_fastener_strength' or 'plasticity_inspect_single_fastener_plate'.

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?

Relevant guidance exists ('For one fastener carrying in-plane plate load, establish the load direction and separate bearing, shear and tensile allowables before calculating. Never substitute compressive strength for bearing strength.' and 'The single-through-fastener plate method assumes one hole; never repeat it per hole'), which is genuine when/how-not content. However it is buried inside a document dominated by other tools' workflows, and no explicit statement distinguishes this tool from the sibling calculate/inspect single-fastener tools.

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