Skip to main content
Glama

Helix developed length

bpj_geom_helix
Read-onlyIdempotent

Calculate helix length, axial travel, and lead angle from radius, pitch, and turns.

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": {
      "radius": "<radius>",
      "pitch": "<pitch>",
      "turns": "<turns>"
    },
    "name": "bpj_geom_helix"
  }
}

Input Schema

NameRequiredDescriptionDefault
pitchYes
turnsYes
radiusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 fully covered. The description adds only that this is a deterministic formula computation returning three derived quantities; it says nothing about unit conventions of outputs or edge-case behavior for degenerate inputs.

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 no filler. Every clause (outputs, then inputs) earns its place in a definition of this size.

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?

With no output schema, the description usefully names the three returned quantities, which is the main thing an agent needs. It falls short only on output units and on whether 'helix length' means developed length or projected length, which matters for a geometry tool.

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 must carry weight; it names all three parameters and ties them to the computed outputs, which is useful mapping. However, it adds no unit or definitional detail beyond what the schema titles already give ('Radius (m)', 'Axial pitch per turn (m)', 'Turns'), leaving the meaning of 'pitch' vs 'lead' unclarified.

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?

States a specific verb (calculate) and three named outputs (helix length, axial travel, lead angle) from three named inputs. A reader knows exactly what comes out, which the tool title alone does not provide.

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 implicitly self-evident for a pure geometry calculator, but there is no explicit statement of when to prefer it over siblings such as bpj_geom_cylinder or bpj_geom_ring_torus, and no exclusions or preconditions.

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.