Skip to main content
Glama

Extrusion bead throughput

bpj_material_print_bead_flow
Read-onlyIdempotent

Estimate volumetric throughput from a rectangular bead approximation, line width, layer height, and travel speed.

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": {
      "width": "<width>",
      "height": "<height>",
      "speed": "<speed>"
    },
    "name": "bpj_material_print_bead_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedYes
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile: read-only, idempotent, closed-world, and non-destructive. The description adds useful context that the result is an estimate based on a rectangular bead approximation, but it does not explain output units, assumptions, or accuracy limits beyond that.

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?

It is a single front-loaded sentence with no filler. Every phrase contributes to identifying the calculation and the parameters involved.

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 simple three-parameter calculator with rich read-only annotations and no output schema, the description is largely sufficient to select and invoke the tool. The main remaining gap is that it does not state the output units or explicit formula, though volumetric throughput in mm³/s is reasonably inferable from the inputs.

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 description coverage is 0%, so the description has to carry parameter meaning. It names the three inputs as line width, layer height, and travel speed, which aligns with the schema titles and adds the rectangular-bead cross-section context, but it never states the actual throughput relationship or output units.

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 resource: estimate volumetric throughput from a rectangular bead approximation. It makes the extrusion/bead domain clear enough, but it does not explicitly distinguish this tool from sibling flow calculators such as pipe flow or general volume-flow utilities.

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?

Usage is implied by 'rectangular bead approximation' and the line width/layer height/travel speed inputs, suggesting this is for extrusion bead throughput estimates. However, the description gives no explicit when-to-use guidance, exclusions, or named alternatives among the many flow-related sibling tools.

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.