Skip to main content
Glama

3D print layer fit

bpj_material_layer_height_plan
Read-onlyIdempotent

Fit a fixed first layer and equal remaining layers under a target maximum height.

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": {
      "height": "<height>",
      "first": "<first>",
      "max": "<max>"
    },
    "name": "bpj_material_layer_height_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxYes
firstYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish a safe, read-only, idempotent calculation. The description adds useful behavioral context by stating that the first layer is fixed and all remaining layers are equal, which tells the agent how the fit is computed. It does not describe the return value or edge cases.

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 contributes to the computation being defined.

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?

For a three-parameter calculator with no output schema and 0% parameter description coverage, the description states the core rule but leaves open what is returned and how edge cases (for example height less than the first layer, or exactly divisible layers) are handled. It is adequate but not complete.

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 parameter meaning. It maps conceptually to 'first', 'height', and the maximum-layer constraint, and crucially adds that remaining layers are equal. However, 'target maximum height' is ambiguous against the schema's separate 'max' (maximum subsequent layer) and 'height' (model height) parameters.

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 uses a specific operation ('Fit') and concrete constraints ('fixed first layer', 'equal remaining layers', 'target maximum height') to state what the tool computes. It does not explicitly distinguish itself from sibling material calculators, but the 3D-printing layer context is clear.

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 the computation described: plan layer heights when the first layer is fixed and remaining layers are equal under a maximum bound. There is no explicit when-to-use guidance, prerequisites, or comparison to sibling planning 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.