Skip to main content
Glama

Future Micro Mold Lab

Cooling-time study

cooling_time
Read-onlyIdempotent

Find the shortest cooling time at which a dimension has stopped changing, and the cycle seconds that come off. Supply the drawing tolerance and the rule tightens to a tenth of it. Measure each part at a consistent interval after ejection — the part keeps moving.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cooling_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsNo
contextNo
study_codeNoA study as the Lab card encodes it; use instead of the measurements (points, dimensionName, dimensionTolerance)
dimensionNameNo
dimensionToleranceNoTotal drawing tolerance, same units as dimension

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this a safe, read-only, idempotent computation, so the description only needs to add behavioral color. It does add one real trait — supplying a drawing tolerance causes the stopping rule to tighten to a tenth of that tolerance — which is genuinely useful context. But it never explains what comes back (no output schema exists) or which of the two input modes to pick.

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?

Three sentences, front-loaded with the outcome before the mechanics, and no filler. The phrasing "the cycle seconds that come off" is slightly idiomatic but still readable in one pass.

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 tool with no required inputs, no output schema, and only 40% schema coverage, the description does an adequate job on purpose and on the tolerance rule. It is still missing the return-value shape and guidance on the alternate study_code path, which an agent needs to call this correctly.

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?

With only 40% schema coverage the description must compensate, and it partly does: it explains that dimensionTolerance drives a tightening rule and that measurements need a consistent post-ejection interval. However, the context object (material, meltTempC, moldTempC) and dimensionName go undocumented in both the schema and description, and the points-vs-study_code choice is left to the schema text.

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 states a specific verb and result: find the shortest cooling time at which a dimension has stopped changing, plus the cycle seconds saved. An agent can tell this is a cooling-time computation rather than a measurement or gage tool, though it never contrasts itself with siblings like viscosity_curve or process_capability.

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 measurement advice ("measure each part at a consistent interval after ejection") but no when-to-use or when-not-to-use guidance, and no pointer to an alternative tool. The choice between the two input modes is not addressed in the description at all.

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.

Resources