Skip to main content
Glama

Freight Allocation by Weight

bpj_freight_allocation_by_weight
Read-onlyIdempotent

Allocate a consolidated freight bill between two shipments in proportion to their measured weights.

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": {
      "base": "<base>",
      "aWeight": "<aWeight>",
      "bWeight": "<bWeight>"
    },
    "name": "bpj_freight_allocation_by_weight"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYes
aWeightYes
bWeightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 safety profile is covered. The description adds the actual allocation rule (proportional to measured weights) but omits rounding/precision, handling of a zero weight sum, and whether the split is returned per shipment.

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?

One front-loaded sentence with no filler; the verb, the resource, and the allocation rule all appear before any qualifying detail.

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?

For a three-parameter pure calculation with no output schema, the description should say what comes back (e.g. allocated amount per shipment) and how rounding is handled; neither appears. The core computation and its inputs are covered, so an agent can call it, but the return shape must be guessed.

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% – only titles like "Base freight" and "Shipment A weight (kg)" exist – so the description must carry the meaning. It does explain that base is the amount to divide and the weights are the proportional basis, though it does not address units beyond the titles or degenerate weight values.

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 concrete verb ("Allocate") and resource ("consolidated freight bill") with the exact rule ("in proportion to their measured weights"), which separates it from weight-related siblings such as bpj_carrier_billable_weight or bpj_design_stock_batch_weight. It never names a sibling, so differentiation is by inference only.

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 two-shipment consolidated-bill scenario is implied clearly enough that an agent can tell when the tool applies. There is no guidance on when not to use it, what to do with zero or missing weights, or which sibling handles a related allocation.

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.