Skip to main content
Glama

Freight Dwell Demurrage

bpj_freight_dwell_demurrage
Read-onlyIdempotent

Deduct the free dwell allowance, then bill each started 24-hour period at the agreed flat daily fee.

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": {
      "dwell": "<dwell>",
      "free": "<free>",
      "perDay": "<perDay>"
    },
    "name": "bpj_freight_dwell_demurrage"
  }
}

Input Schema

NameRequiredDescriptionDefault
freeYes
dwellYes
perDayYes

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 this a read-only, idempotent, non-destructive, closed-world operation, which is consistent with a pure arithmetic helper. The description adds real behavioral detail beyond that: the free allowance is deducted first and billing is per *started* period, implying ceiling rounding. However, it never states what is returned (a currency amount? a day count?) and there is no output schema to fill that gap.

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 well-ordered sentence that front-loads the deduction step and then the billing step, mirroring the computation order. No padding or restatement of the title.

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 three-parameter arithmetic utility with annotations covering safety and no nested structures, the description supplies the essential algorithm. The remaining gap is the return format and the zero-charge boundary case, which matters somewhat given no output schema exists.

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 0%, so the description must carry the semantic load, and it does establish the relationship among the three inputs (dwell minus free, then per-day fee). It does not reinforce the units in hours or clarify that perDay is charged once per partially-started day, which is exactly the kind of detail an agent could get wrong.

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 names specific operations on a specific resource: deducting the free dwell allowance and billing started 24-hour periods at a flat daily fee. An agent can tell this is a demurrage charge calculator rather than, say, a surcharge stacker or weight allocation. It stops short of naming a return value, but the purpose is unmistakable.

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 calculation logic implies the usage context (freight billing where dwell exceeds free time), but there is no explicit when-to-use statement, no mention of what happens when dwell is below the free allowance, and no routing to or away from any sibling tool. Usage is inferred rather than stated.

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.