Skip to main content
Glama

Future Micro Mold Lab

Cavity balance study

cavity_balance
Read-onlyIdempotent

Quantify cavity-to-cavity fill imbalance from short-shot weights. Give two or more replicate shots at a fill level and the result also says whether the variation comes from the cavities (runner and gate geometry) or from shot-to-shot process drift — the two have opposite fixes. Judge balance on a short shot at 90% fill or above.

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": "cavity_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelsNoOne entry per fill percentage tested — e.g. a 50%, then a 95%, short shot.
contextNo
study_codeNoA study as the Lab card encodes it; use instead of the measurements (levels)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotation set already declares readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the agent knows the safety and repeatability profile. The description adds genuinely non-obvious behavior: with two or more replicates the result also attributes variation to cavity/runner/gate geometry versus shot-to-shot process drift, and those have opposite fixes. It does not state the actual return shape or how results are keyed per cavity, which leaves a gap for a tool with no output schema.

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?

Three sentences, front-loaded with the purpose, then the payoff, then the validity condition. Nothing is redundant and no sentence restates the name or annotations.

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, idempotent analysis tool with nested objects but no output schema, the description covers the method, the prerequisite replicate count, and what the result distinguishes. The main omission is the alternate study_code input path and the context fields (material, melt/mold temps), which an agent would have to discover from the schema alone.

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?

The description adds a real constraint beyond the schema: the schema permits shots with minItems 1, but the description requires two or more replicates for the variance-attribution feature. That detail is genuinely valuable. However, the study_code parameter, which the schema says should be used 'instead of the measurements (levels)', and the context object are never addressed, so a meaningful share of the semantics remains undocumented.

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?

The description opens with a specific verb and resource: 'Quantify cavity-to-cavity fill imbalance from short-shot weights.' It names the input (short-shot weights) and the output measure (fill imbalance), which is concrete enough to distinguish it from every sibling listed (pressure_drop, gate_seal, cooling_time, etc.).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete precondition — 'Give two or more replicate shots at a fill level' — and a validity rule: 'Judge balance on a short shot at 90% fill or above.' That tells the agent when results are trustworthy. It stops short of naming an alternative tool or stating when not to use it, so it falls short of an explicit when/when-not/alternatives pair.

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