Skip to main content
Glama

Loose-fill material weight

bpj_material_loose_fill
Read-onlyIdempotent

Estimate loose-fill volume and mass from surface area, depth, and supplier bulk density.

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>",
      "depth": "<depth>",
      "density": "<density>"
    },
    "name": "bpj_material_loose_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYes
depthYes
densityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds that the result is an estimate and that density comes from the supplier, but it omits assumptions, rounding, and output units; there is no contradiction with annotations.

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?

One front-loaded sentence with no filler. It is appropriately sized for a simple three-parameter calculator.

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 description states the outputs (volume and mass) and inputs, but it does not give output units or note that the calculation is an estimate with rounding. Annotations cover safety, but the return-value semantics are incomplete.

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 parameter meaning. It maps the three inputs to 'surface area', 'depth', and 'supplier bulk density', but it does not specify units (m2, mm, kg/m3), constraints, or how depth and density combine, leaving the schema titles to do most of the work.

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 names the exact outputs ('loose-fill volume and mass') plus the three inputs, so the agent can tell this is a material-quantity calculator rather than a generic fill or weight tool. It does not explicitly distinguish itself from sibling material calculators, but 'loose-fill' is a narrow resource label.

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?

No guidance is given on when to choose this over sibling material calculators (e.g., shrink-fill, concrete bag yield) or when it is inappropriate. The use case is inferable from the purpose, but the description provides no explicit conditions or 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.