Skip to main content
Glama

Future Micro Mold Lab

Pressure-drop study

pressure_drop
Read-onlyIdempotent

Find where injection pressure is consumed along the flow path. Each reading is the CUMULATIVE peak pressure needed to fill through that section — an air shot gives the nozzle figure, then sprue, runner, gate and the full part — so the values ascend. Known sections: Nozzle, Sprue, Runner, Gate, Part. Run every reading at the velocity the viscosity curve selected.

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

Input Schema

NameRequiredDescriptionDefault
stagesNo
contextNo
study_codeNoA study as the Lab card encodes it; use instead of the measurements (stages, machineMaxPressure, intensificationRatio)
machineMaxPressureNoMachine maximum injection pressure, same units as pressure
intensificationRatioNoHydraulic-to-plastic multiplier; omit if pressure is already plastic

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful semantics — the values are cumulative and therefore ascend, and the nozzle figure comes from an air shot — which prevents misreading the data. It does not say what the tool returns (a per-section drop? a bottleneck section?) and does not explain the study_code versus explicit-measurements path, which is the main behavioral ambiguity.

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?

Four tight sentences, front-loaded with the purpose and then the key data-interpretation caveat. The section list slightly duplicates the schema's enum-like hint, but overall there is little waste.

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?

With five parameters, a nested object, two optional input paths, and no output schema, the description leaves important gaps: it never says what the result looks like (per-section drop versus identification of the constraining section) and never mentions the context block. It is adequate to understand the measurement concept but not fully sufficient to call the tool confidently.

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 coverage is 60%, and the schema itself documents study_code, machineMaxPressure, intensificationRatio and the stage name examples. The description reinforces the cumulative/ascending meaning of the pressure field, which is real added value, but it says nothing about the context object (material, meltTempC, moldTempC) or how machineMaxPressure and intensificationRatio affect interpretation.

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 analytical intent — locating where injection pressure is consumed along the flow path — which is more than a restatement of the name. It does not, however, distinguish itself from siblings like cavity_balance or gate_seal, which also analyze stages of the process; the viscosity_curve mention is a procedural reference, not a routing alternative.

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?

There is a concrete procedural constraint: run every reading at the velocity the viscosity curve selected. That tells the agent how the data must be gathered but not when this tool should be chosen over the other study tools, nor any exclusions or prerequisites.

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