Skip to main content
Glama

Bagged mix yield

bpj_material_concrete_bag_yield
Read-onlyIdempotent

Estimate mix bags for a rectangular pour from its volume, allowance, and the manufacturer’s finished yield per bag.

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>",
      "thickness": "<thickness>",
      "waste": "<waste>",
      "bag": "<bag>"
    },
    "name": "bpj_material_concrete_bag_yield"
  }
}

Input Schema

NameRequiredDescriptionDefault
bagYes
wasteYes
widthYes
lengthYes
thicknessYes

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?

The annotations already establish that this is a safe read-only, idempotent, non-destructive calculation. The description adds useful domain context about volume, waste allowance, and manufacturer yield, but it does not state output rounding, unit conversion behavior, or validation assumptions.

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. Every phrase contributes to identifying the calculation and its key inputs.

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 read-only calculator whose annotations already cover safety, the description conveys the core estimation concept but omits important invocation details such as unit conversion between metres and millimetres and whether the result is rounded up to whole bags.

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%, so the description must compensate, and it partially does by framing the inputs as volume, allowance, and finished yield per bag. However, it does not explain how width, length, and thickness produce the volume, nor does it highlight the mixed units (m for width/length, mm for thickness, % for waste, L/bag for yield).

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, 'Estimate', and a specific resource, 'mix bags for a rectangular pour', with the key inputs named as volume, allowance, and finished yield per bag. It is clear what the tool computes, but it does not explicitly distinguish itself from the many sibling material calculators.

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 rectangular pour' implies the context in which this calculator applies, but there is no explicit when-to-use guidance, no exclusions, and no named alternative for non-rectangular pours or other bag-estimation cases.

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.