Skip to main content
Glama

Scrap and Rework Loss

bpj_scrap_rework_loss
Read-onlyIdempotent

Value disjoint scrapped and reworked units using net scrap loss and incremental rework cost per unit.

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": {
      "total": "<total>",
      "scrap": "<scrap>",
      "wasteCost": "<wasteCost>",
      "rework": "<rework>",
      "reworkCost": "<reworkCost>"
    },
    "name": "bpj_scrap_rework_loss"
  }
}

Input Schema

NameRequiredDescriptionDefault
scrapYes
totalYes
reworkYes
wasteCostYes
reworkCostYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 a closed world, so the safety profile is fully covered and the description is not required to restate it. The description adds the valuation concept — net scrap loss plus incremental rework cost — but is silent on the actual combination rule, on whether scrap and rework units must be disjoint subsets of total, and on what is returned.

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?

One sentence with no filler and the key concept front-loaded — economical and easy to scan. Its density of undefined jargon ('disjoint', 'net scrap loss') costs a point on immediate comprehensibility.

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?

With five required parameters, 0% schema description coverage and no output schema, the definition should explain the formula and the input constraints. It instead leaves the agent to guess how the four inputs combine into a value and what the result represents.

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 the burden, and it only loosely maps 'net scrap loss' to wasteCost and 'incremental rework cost per unit' to reworkCost. It never clarifies the relationship between total, scrap and rework (subsets? mutually exclusive? can scrap + rework exceed total?), which is the main ambiguity in a 5-required-parameter tool.

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 gives a specific verb ('Value') and a specific resource ('disjoint scrapped and reworked units'), tied to the cost inputs used. It does not, however, differentiate itself from the many other loss/cost calculators among its siblings, and the word 'disjoint' is unexplained jargon.

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 guidance, no prerequisites, and no mention of when another tool (e.g. a plain scrap-cost or rework-cost calculator) would be preferable. The agent must infer the applicable scenario entirely from the tool name and inputs.

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.