Skip to main content
Glama

Seal Check

seal_check
Read-only

Validate O-ring gland designs by calculating squeeze and fill percentages against static or dynamic application limits, returning pass/fail results.

Instructions

Rate an O-ring gland (pairs with oring_groove): squeeze=W-depth, fill= (pi/4 W^2)/(width*depth). Squeeze must sit in the application band (static 15-30%, dynamic 10-20%), fill below max_gland_fill_pct. Returns {squeeze_mm, squeeze_pct, gland_fill_pct, squeeze_range_pct, within_squeeze, within_fill, pass}.

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": {
      "cross_section_dia_mm": "<cross_section_dia_mm>",
      "groove_depth_mm": "<groove_depth_mm>",
      "groove_width_mm": "<groove_width_mm>"
    },
    "name": "seal_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoRun this call in this named workspace
applicationNostatic_radial
groove_depth_mmYes
groove_width_mmYes
max_gland_fill_pctNo
cross_section_dia_mmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description correctly does not contradict them. It adds real value beyond them by disclosing the acceptance thresholds (static 15-30%, dynamic 10-20%, fill under max_gland_fill_pct) and by enumerating the returned verdict fields, so the agent knows this returns a boolean gate rather than raw geometry.

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?

Two dense sentences that front-load the purpose, then the math, then the return shape — nothing redundant. The notation is terse enough ("pi/4 W^2") that parsing costs a moment, but every clause earns its place.

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 read-only calculator with no output schema, the description lists the return keys and the pass/fail semantics, which is the critical missing piece. Remaining gaps are the enumeration of valid 'application' values and any note on units/valid input ranges, minor for a pure computation tool.

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?

With only 17% schema coverage, the description carries the burden and largely does: the formulas bind the parameters to roles (W = cross_section_dia_mm, groove_depth_mm drives squeeze, groove_width_mm plus W drives fill), and max_gland_fill_pct gets meaning as a threshold. It leaves 'application' and 'workspace' under-specified, and the valid values for application (static vs dynamic vs the schema default 'static_radial') are never enumerated.

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

Purpose5/5

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

Opens with a specific verb+resource ("Rate an O-ring gland") and immediately scopes it against the sibling ("pairs with oring_groove"), so an agent knows this is the verification step for a groove, not the groove creator. It also gives the exact formulas used, removing all ambiguity about what is being computed.

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?

"pairs with oring_groove" and the stated acceptance bands imply the workflow (create groove, then check it) and tell the agent what the pass criteria are, including per-application thresholds. But it never explicitly says when to call this versus oring_groove or what to do on failure, leaving the sequencing to inference.

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