Skip to main content
Glama

Carrier Billable Weight

bpj_carrier_billable_weight
Read-onlyIdempotent

Compare dimensional and scale weight using the carrier divisor, then round up to its billing increment.

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": {
      "length": "<length>",
      "width": "<width>",
      "height": "<height>",
      "divisor": "<divisor>",
      "weight": "<weight>",
      "step": "<step>"
    },
    "name": "bpj_carrier_billable_weight"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepYes
widthYes
heightYes
lengthYes
weightYes
divisorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/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 safety and determinism are covered. The description adds the computational rule (compare then round up), which is useful behavior beyond annotations. It omits what the rounding rule does at exact ties and whether the larger of the two weights is the returned value, leaving the core decision implicit.

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, and the compute order (compare, then round up) is front-loaded so the agent can follow the algorithm immediately. Nothing is redundant with the title or annotations.

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?

With no output schema, the description should say what comes back — a single kilogram figure versus an object containing dimensional, scale and billable weights — and it does not. For a six-required-parameter calculator with 0% schema coverage, that leaves a meaningful gap in an otherwise complete definition.

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 reported as 0%, so the description must carry the meaning; it partly does by tying the divisor to dimensional weight and the step to the billing increment. Units such as cm, kg and cm³/kg appear only in schema titles, not in the description, and the dimensional-weight formula (L×W×H/divisor) is implied rather than stated. This is partial compensation, not full.

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 states a specific operation: compare dimensional weight against scale weight using a carrier divisor and round up to the billing increment. That is a concrete verb-plus-computation, not a restatement of the name. It does not, however, differentiate itself from weight-adjacent siblings such as bpj_freight_allocation_by_weight or bpj_design_stock_batch_weight.

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 explicit when-to-use guidance, no statement of prerequisites (e.g. that a carrier-specific divisor and increment must be supplied), and no named alternative. The agent must infer applicability from the title alone.

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.