Skip to main content
Glama

Straight fence post spacing

bpj_material_fence_posts
Read-onlyIdempotent

Divide an open straight fence without gates into equal bays under a maximum post spacing, including both ends.

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": {
      "length": "<length>",
      "maxSpan": "<maxSpan>"
    },
    "name": "bpj_material_fence_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthYes
maxSpanYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the read-only, idempotent, and non-destructive annotations, it discloses the equal-bay strategy, maximum-spacing constraint, and inclusion of both ends. It does not explicitly state the bay-count rounding rule or the returned results, which prevents a higher score.

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 compact sentence front-loads the task and efficiently includes the scope, equal-spacing behavior, maximum constraint, and endpoint rule. There is no filler or redundant wording.

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 simple two-number calculator, the description provides enough context to select the tool and supply its inputs, while the annotations cover its safety profile. Because there is no output schema, the absence of any statement about returned post count, bay count, or actual spacing leaves a noticeable completeness gap.

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?

Despite 0% schema description coverage, the wording makes 'length' the total open fence run and 'maxSpan' the upper bound on spacing, while explaining how they relate. Explicitly stating that the bay count is rounded up so actual spacing never exceeds 'maxSpan' would make the semantics fully precise.

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?

The description specifies the exact task: dividing an open, straight, gate-free fence into equal bays subject to a maximum post spacing. The fence-specific scope and endpoint rule distinguish it from sibling spacing calculators for balusters, seeds, or shelf holes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrases 'open straight fence' and 'without gates' clearly establish applicability and exclude gated runs. It does not explain how to handle gated or multi-segment fences or name an alternative, so the guidance is not exhaustive.

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.