Skip to main content
Glama

Freight Surcharge Stack

bpj_freight_surcharge_stack
Read-onlyIdempotent

Apply the fuel percentage only to base freight, then add fixed residential and remote-area charges.

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>",
      "fuel": "<fuel>",
      "residential": "<residential>",
      "area": "<area>"
    },
    "name": "bpj_freight_surcharge_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYes
baseYes
fuelYes
residentialYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description does add genuine behavioral detail — that the fuel percentage is scoped to base freight only and the other two charges are fixed additions — but says nothing about units/currency or how the result 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with two ordered clauses, front-loading the key scoping rule (fuel on base only) and then the additive step. No filler, nothing repeated from the schema.

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

Completeness4/5

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

For a four-parameter arithmetic tool with no output schema, the description supplies the essential computation logic and the parameter roles. The remaining gap is that it never states what the tool returns (a single total, presumably) or the assumed currency, which an agent would need. Wait — that gap is real, so the score stays at 4 only because the formula itself is fully specified.

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 carries the full burden, and it does clarify that 'fuel' is a percentage applied to 'base' only while 'residential' and 'area' are fixed additive charges. This maps meaning onto all four parameters, though it omits currency units and whether 'area' is a fee amount or a lookup key.

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 computation with an ordering rule ('apply the fuel percentage only to base freight, then add...'), which tells an agent exactly what the tool does rather than restating the name. It does not explicitly differentiate itself from freight-related siblings such as bpj_freight_allocation_by_weight, leaving that to the name alone.

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: the sentence reads as a calculation recipe, so an agent can infer this is a rate-stacking calculator rather than an allocator. There is no explicit statement of when to choose it over freight siblings and no exclusions or prerequisites.

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.