Skip to main content
Glama

Even slat spacing

bpj_material_baluster_spacing
Read-onlyIdempotent

Find the fewest equal-width slats that meet a chosen clear-gap maximum, including equal end gaps.

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": {
      "opening": "<opening>",
      "slat": "<slat>",
      "gap": "<gap>"
    },
    "name": "bpj_material_baluster_spacing"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapYes
slatYes
openingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is fully covered and the description need not restate it. The text adds the real behavioral kernel — minimize slat count, force equal spacing including end gaps — but with no output schema it never says what is returned (count only, or count plus achieved gap and end-gap values).

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 zero filler; every clause carries information (minimization, equal widths, gap ceiling, end gaps). Nothing could be removed without losing meaning.

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-required-parameter arithmetic tool with full annotation coverage, the definition is nearly adequate, but the absent output schema leaves the return shape unexplained and no edge-case behavior (slat wider than opening, integer rounding of slat count) is described.

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%, but each property carries a title with units (mm) for gap, slat and opening. The description reinforces the gap semantics by calling it a 'clear-gap maximum' and implying a shared end gap, yet it adds no guidance on units, sensible ranges, or what happens when the slat exceeds the opening; partial compensation only.

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?

Names a specific computation: the fewest equal-width slats satisfying a clear-gap maximum, plus equal end gaps. That is concrete enough to distinguish it from a generic spacing helper, though it never explicitly contrasts itself with siblings like bpj_material_seed_spacing or bpj_material_tile_joint_grid.

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 by the word 'baluster' in the name and the slat/gap framing; the description itself states no when-to-use condition, no prerequisites, and no alternatives. For a single-purpose calculator this is tolerable, but an agent gets no routing guidance from the text.

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.