Skip to main content
Glama

3D filament spool length

bpj_material_filament_spool
Read-onlyIdempotent

Estimate available filament length from net spool mass, measured diameter, and polymer density.

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": {
      "mass": "<mass>",
      "diameter": "<diameter>",
      "density": "<density>"
    },
    "name": "bpj_material_filament_spool"
  }
}

Input Schema

NameRequiredDescriptionDefault
massYes
densityYes
diameterYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds only the word "Estimate", which usefully signals an approximation rather than an exact measurement, but it omits the underlying assumption (round cross-section, ideal diameter) and any accuracy caveat.

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?

A single front-loaded sentence with the output quantity stated first and the inputs after; every word earns its place and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should say what comes back, notably the unit of the returned length (m vs mm) and the geometric model assumed. For a physics-based estimator those omissions materially affect how an agent interprets and reports the result.

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%, though each property carries a title with units (g, g/cm3, mm). The description names all three inputs ("net spool mass, measured diameter, and polymer density") and maps them to the parameters, but adds no format, range or modeling detail beyond the titles, so it only partially compensates.

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?

States a specific verb ("Estimate") and resource ("available filament length") plus the three inputs that drive it, so an agent knows exactly what the tool computes. It does not distinguish itself from plausible siblings such as bpj_material_roll_remaining or bpj_material_print_bead_flow, leaving overlap resolution to the caller.

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 no when-to-use or when-not-to-use guidance and no mention of alternatives in a dense family of material calculators. The only implied context is that you must already know the spool mass, filament diameter and polymer density, which the required-parameter list covers anyway.

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.