Skip to main content
Glama

Evenly spaced hole positions

bpj_material_even_shelf_holes
Read-onlyIdempotent

Determine pitch and the middle pair of hole-center coordinates between symmetric end offsets.

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": {
      "span": "<span>",
      "edge": "<edge>",
      "holes": "<holes>"
    },
    "name": "bpj_material_even_shelf_holes"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgeYes
spanYes
holesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation. The description adds useful context about symmetric end offsets and the computed pitch/middle-pair, but it does not describe return structure, formula assumptions, or how odd hole counts 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no filler or repetition. It is concise, though the compressed phrase 'middle pair' is terse enough to be somewhat opaque.

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?

For a pure calculation tool with three required parameters and no output schema, the description gives only a partial account of what is returned. It does not explain the coordinate system, output format, or behavior when the hole count is odd, which matters because 'middle pair' implies an even count while the schema allows any integer from 2 upward.

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

Parameters2/5

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

Schema description coverage is 0%, so the description needs to carry parameter meaning. It hints at 'end offsets' and symmetric placement, but does not explicitly map span, edge, and holes to the pitch and coordinate outputs, leaving the required parameter relationships underspecified.

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 verb and resource: 'Determine pitch and the middle pair of hole-center coordinates.' It is clear what computation is performed, though it does not explicitly differentiate itself from sibling material-spacing calculators by name.

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 explicit when-to-use guidance, no conditions for choosing this tool over alternatives, and no stated prerequisites. The description only implies usage by stating what it computes.

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.