Skip to main content
Glama

Rectangular planting grid

bpj_material_seed_spacing
Read-onlyIdempotent

Count planting positions on a rectangular grid, with the first row and plant centered half a spacing from the edge and matching clearance at the far side.

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": {
      "width": "<width>",
      "length": "<length>",
      "row": "<row>",
      "plant": "<plant>"
    },
    "name": "bpj_material_seed_spacing"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowYes
plantYes
widthYes
lengthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/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 covered. The description adds genuinely non-obvious behavioral detail not in the schema or annotations: the half-spacing offset from the edge and the matching clearance at the far side, which defines the counting convention. It omits rounding/floor behavior and what exactly is returned beyond an implied count.

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?

A single front-loaded sentence with no filler; the counting convention is attached immediately rather than buried. The phrasing 'the first row and plant centered' is slightly awkward and requires a re-read, but nothing is wasted.

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 four-parameter numeric calculator with no output schema and 0% parameter documentation, the definition covers the geometric convention but not the arithmetic outcome — whether the result is a per-axis count, a total, or how sub-spacing dimensions are floored. An agent can call it correctly, but cannot predict the result precisely.

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% — the parameters carry only titles ('Row spacing (m)', 'In-row spacing (m)', 'Width (m)', 'Length (m)'). The description clarifies that 'row' governs the first-row offset and 'plant' the in-row centering, and that width/length are the bounded extents, which is meaningful compensation, but it never states the relationship explicitly enough to be more than partial.

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 names a specific verb ('Count') and resource ('planting positions on a rectangular grid'), which an agent can distinguish from siblings like tile_joint_grid or baluster_spacing. It stops short of explicitly contrasting itself with those siblings, but the purpose is unambiguous.

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 when-to-use / when-not-to-use guidance and no named alternative among the many grid/spacing siblings. Usage is only implied by the phrase 'planting positions', leaving the agent to infer that this is a material takeoff calculation versus a geometry generator.

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.