Skip to main content
Glama

Adhesive coverage by spread

bpj_material_adhesive_spread
Read-onlyIdempotent

Find one-face coverage available from adhesive mass at a target spread and usable 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": {
      "mass": "<mass>",
      "spread": "<spread>",
      "yield": "<yield>"
    },
    "name": "bpj_material_adhesive_spread"
  }
}

Input Schema

NameRequiredDescriptionDefault
massYes
yieldYes
spreadYes

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the agent knows this is a safe, deterministic, closed-form computation. The description adds only the notion that the result is 'one-face' coverage derived from mass, spread and yield, but discloses nothing about how yield is applied, rounding, or the unit of the returned area.

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 or redundancy. It is efficient, though its brevity leaves useful computation details unstated.

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?

No output schema exists, so the description is the only place to state what is returned; it never specifies the output unit (presumably m²) or the formula relating the three inputs. For a pure calculator whose correctness depends on understanding how yield and spread interact, that is a meaningful omission.

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%, and only the schema titles carry units (kg, %, g/m2). The description restates the three parameter names but does not explain the relationship — e.g., that usable yield reduces effective mass and coverage = mass × yield / spread — nor whether spread is the target applied rate. It therefore does not compensate for the missing schema documentation.

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 computation: one-face coverage obtainable from adhesive mass given a target spread and usable yield. The verb 'find' plus the domain term 'adhesive' clearly separates it from the many other coverage calculators in the sibling list (brick, fence, paint, etc.), though it does not name or contrast any sibling explicitly.

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 one-line purpose implies when the tool applies (sizing adhesive for a given spread and mass), but there is no explicit when-to-use/when-not-to-use guidance and no pointer to alternatives such as a reverse calculation (spread from required coverage) or a different material coverage tool. Usage is inferable from the domain rather than stated.

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.