Skip to main content
Glama

Future Micro Mold Lab

Viscosity curve study

viscosity_curve
Read-onlyIdempotent

Find the optimal injection velocity from a velocity / peak-pressure sweep. Computes relative viscosity (plastic pressure times fill time) against relative shear rate, locates the shear-thinning plateau, and picks a velocity from the middle of it. Record a fill time on every point for a result that transfers between machines. This is the first study in the sequence; every later study holds its velocity constant.

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

Input Schema

NameRequiredDescriptionDefault
pointsNo
contextNo
study_codeNoA study as the Lab card encodes it; use instead of the measurements (points, intensificationRatio, machineMaxPressure)
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

A4.2/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent operation. Beyond that, the description discloses meaningful behavior: it computes relative viscosity against relative shear rate, locates the shear-thinning plateau, and selects a velocity from the middle of it. It does not cover error conditions, output format, or what happens if no plateau is found.

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?

The description is front-loaded with the main purpose and method, then adds only the important data-quality note about fill time and the sequencing context. Every sentence contributes useful information without redundant wording.

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 moderately complex tool with nested point data and no output schema, the description adequately explains the study's purpose, method, and place in the workflow. It leaves some gaps around the exact return value and the relationship between measurement-based input and study_code, but the core invocation context is present.

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 useful meaning to velocity, pressure, and fillTime by explaining the viscosity calculation and emphasizing that fill time should be recorded on every point. However, it does not explain study_code, machineMaxPressure, intensificationRatio, or context, leaving several parameters covered only by the schema.

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 gives a specific verb and resource: find the optimal injection velocity from a velocity/peak-pressure sweep. It also explains the underlying calculation and explicitly distinguishes this as the first study in the sequence, setting it apart from later studies that hold velocity constant.

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?

The description clearly places the tool as the first study in the sequence and notes that later studies hold velocity constant, which tells the agent when this tool applies. It does not explicitly name alternative sibling tools or state when not to use it, so it falls short of a full 5.

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