Skip to main content
Glama

BRAINIAC Maritime & Shipping Intelligence

Calculate demurrage cost

maritime-intelligence_demurrage-cost-calculate

Calculate demurrage from caller-supplied allowed/used laytime and daily rate. Results are not legal invoices. Price $0.03 USDC. POST /api/v1/maritime-intelligence/demurrage-cost-calculate. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "maritime-intelligence_demurrage-cost-calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
fileNo
jsonNo
textNo
filesNo
vesselsNo
aisPointsNo
fetchOfacNo
waypointsNo
cargoEventsNo
portSamplesNo
assumedSpeedKnNo
demurrageCasesNo
destinationLatNo
destinationLonNo
ownershipRecordsNo
sanctionsEntriesNo
gapThresholdHoursNo
deviationThresholdKmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose non-obvious behavior: a $0.03 USDC price, that unpaid calls return 402 and do not run, and that results are not legal invoices. It says nothing about determinism, what is returned, or how the many non-laytime inputs affect the result, so the safety/payment profile is covered but output behavior is not.

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?

Four short sentences, each carrying distinct information (purpose, legal caveat, price, transport/payment behavior) with the core function front-loaded. No filler, though the raw endpoint path is low-value for an agent.

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?

This is a 20-parameter tool with nested objects, no annotations and no output schema, yet the description explains only a small slice of the input surface and nothing about the return value. For a paid, complex analytical call, an agent still cannot tell what shape of input will actually produce a demurrage figure.

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% across 20 parameters, including nested files, vessels, aisPoints, portSamples and demurrageCases. The description accounts for only the laytime and rate concepts and gives no guidance on which of csv/json/text/file/files forms to supply, what asOf does, or why AIS and sanctions data belong in a cost calculation.

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 specific verb+resource ('Calculate demurrage') and the exact inputs used ('caller-supplied allowed/used laytime and daily rate'), which distinguishes it from every listed sibling such as eta-estimate or voyage-risk-report. It stops short of explicitly naming a sibling it is often confused with, so 4 rather than 5.

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 phrase 'from caller-supplied allowed/used laytime and daily rate' implies the caller must already hold laytime figures rather than have the tool derive them, which is real usage context. There is no explicit when-not-to-use or pointer to an alternative for related voyage risk or congestion analysis.

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.

Resources