Skip to main content
Glama

Compacted fill delivery

bpj_material_shrinkage_fill
Read-onlyIdempotent

Calculate loose delivery volume from a target compacted volume and shrinkage measured against loose volume.

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": {
      "target": "<target>",
      "shrink": "<shrink>"
    },
    "name": "bpj_material_shrinkage_fill"
  }
}

Input Schema

NameRequiredDescriptionDefault
shrinkYes
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this a pure read-only, idempotent, closed-world, non-destructive calculation, so the safety profile is fully covered. The description adds one genuinely useful behavioral fact — that shrinkage is expressed relative to the LOOSE volume, not the compacted volume, which changes the arithmetic. It stops short of stating the actual relationship or the units of the returned value.

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?

A single sentence with no filler, front-loaded with the verb and the computed output. Every clause carries information: the result, the first input, and the reference basis for the second input.

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

Completeness5/5

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

For a two-parameter, read-only arithmetic tool with no output schema, the definition supplies the output identity, both input roles, and the shrinkage reference basis. Given annotations cover the safety profile and the schema carries units and ranges, nothing essential for a correct call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 the semantic load, and it does clarify the critical ambiguity: 'shrink' is measured against loose volume, not against the target. Schema titles supply units (%) and (m3) plus bounds, so the combination is close to complete, but the description does not restate units or explain how the two values combine.

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 ('Calculate') and names the exact output ('loose delivery volume') plus both inputs ('target compacted volume', 'shrinkage measured against loose volume'). An agent can tell this is a compaction/shrinkage conversion rather than a plain volume lookup, though it never explicitly distinguishes itself from the similarly named sibling bpj_material_loose_fill.

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?

Usage is only implied by the input vocabulary: 'target compacted volume' signals the spec-side scenario where you know the finished volume and need the delivered loose volume. There is no explicit when-to-use/when-not statement and no pointer to the sibling tool for the reverse or unfactored calculation.

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.