Skip to main content
Glama

Single-leaf brick count

bpj_material_brick_coverage
Read-onlyIdempotent

Estimate face bricks for a single leaf by modular face area including one mortar joint per axis.

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": {
      "area": "<area>",
      "brickW": "<brickW>",
      "brickH": "<brickH>",
      "joint": "<joint>",
      "waste": "<waste>"
    },
    "name": "bpj_material_brick_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYes
jointYes
wasteYes
brickHYes
brickWYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, idempotent, non-destructive calculation. The description adds method-level context by stating that modular face area includes one mortar joint per axis, but it does not explain how waste is applied, whether the result is rounded, or what exactly is returned.

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?

The definition is a single front-loaded sentence with no filler. It states the estimation target and key method immediately.

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 calculator with no output schema, the definition is adequate for identifying the tool, and the annotations cover safety behavior. It is still missing important operational details such as waste handling, rounding, and return-value semantics, which an agent would need for precise interpretation.

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 must carry more weight for five required parameters. It only indirectly explains the joint parameter and the general face-area calculation, while leaving area, brick width/height, and waste application semantics largely to schema titles and units.

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 gives a specific verb and resource: 'Estimate face bricks for a single leaf' using 'modular face area including one mortar joint per axis.' It clearly identifies the calculation scope, though it does not explicitly differentiate this from any sibling estimator.

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?

The phrase 'for a single leaf' implies the applicable construction case and implicitly excludes multi-leaf or other masonry scenarios. However, it provides no explicit when-to-use guidance, exclusions, prerequisites, or comparison to alternatives.

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.