Skip to main content
Glama

Single-layer spool winding

bpj_material_coil_winding_space
Read-onlyIdempotent

Estimate whole turns and helical line length for one close-packed layer on a cylindrical core.

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>",
      "line": "<line>",
      "core": "<core>"
    },
    "name": "bpj_material_coil_winding_space"
  }
}

Input Schema

NameRequiredDescriptionDefault
coreYes
lineYes
widthYes

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 declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the result is an estimate and that the model is a single close-packed layer, which is useful behavioral context, but it says nothing about precision limits or how edge effects are handled.

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?

One sentence, front-loaded with the computed outputs and immediately followed by the geometric scope. Nothing is redundant.

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?

The description names the two returned values, which helps because there is no output schema, but for a tool whose inputs are entirely undocumented at 0% coverage it leaves unit expectations and the meaning of 'usable winding width' unstated. Adequate for a simple formula, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with 3 required parameters, but the description does state the core and line, and the layer geometry it computes. It doesn't explain usable width or unit assumptions, so a little meaning is added without compensating for the coverage gap.

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?

Specific verb and resource: 'Estimate whole turns and helical line length for one close-packed layer on a cylindrical core.' It states the computed quantities and the geometric scope, which distinguishes it from material siblings like filament_spool, though it never names an 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?

Usage is only implied through the scope phrase 'one close-packed layer on a cylindrical core', which does tell the agent when the calculation applies and when it does not. There is no explicit guidance on when to pick this over other material-estimation siblings or on prerequisites such as units.

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.