Skip to main content
Glama

Sealant cartridge yield

bpj_material_sealant_cartridge
Read-onlyIdempotent

Estimate filled joint length from cartridge volume, rectangular joint dimensions, and available yield.

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": {
      "cartridge": "<cartridge>",
      "width": "<width>",
      "depth": "<depth>",
      "yield": "<yield>"
    },
    "name": "bpj_material_sealant_cartridge"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthYes
widthYes
yieldYes
cartridgeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered and the description adds nothing there. It also fails to disclose the unit and form of the result (linear mm vs m) despite there being no output schema, and does not clarify whether 'available yield' already accounts for waste or whether rounding occurs.

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 tight sentence with the estimated output front-loaded and the inputs enumerated afterward; nothing is wasted. It is efficient, though it is the only sentence and a short clause on result units would have been worth the space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a pure calculator with no output schema and 0% schema description coverage, the description should state the result's unit and formula behavior. It documents the inputs implicitly but leaves the return value entirely unspecified, which is the single most important gap for an agent consuming this tool.

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%, but the four parameters are fully required and their titles carry units ('Joint depth (mm)', 'Joint width (mm)', 'Usable yield (%)', 'Cartridge volume (mL)'). The description restates the four inputs and adds the meaningful 'rectangular joint' framing, but supplies no extra semantics such as expected ranges, typical yield values, or unit conversion behavior beyond the titles.

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?

States a specific verb ('Estimate') and a specific output resource ('filled joint length'), and names the three inputs it derives from, so an agent knows exactly what computation happens. It does not name a sibling (e.g. bpj_material_concrete_bag_yield) to distinguish when this yield estator applies versus other material-yield tools, so it stops short of a 5.

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, or alternative guidance. The description only implies usage through the word 'Estimate'; it never says whether this is for sealant/caulk cartridges specifically, what the rectangular joint assumption covers, or what tools to use for non-rectangular joints.

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.