WritersLogic business agents

storage-charge-clock

Storage, demurrage or detention charge: free-time end date, chargeable days and tiered amount — Counts days between a received date and a released date for storage, demurrage, detention or parking charges: you state whether the receipt day and the release day count, how free days are counted (calendar or business days on a named or caller calendar), and a tiered per-day rate schedule by chargeable day number; returns the last free day, chargeable days, a per-tier breakdown and the total in m

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": {
      "receivedOn": "<receivedOn>",
      "releasedOn": "<releasedOn>",
      "receiptDayCounts": "<receiptDayCounts>",
      "releaseDayCounts": "<releaseDayCounts>",
      "freeDays": "<freeDays>",
      "freeCounting": "<freeCounting>",
      "chargeCounting": "<chargeCounting>",
      "tiers": "<tiers>",
      "currency": "<currency>"
    },
    "name": "storage-charge-clock"
  }
}

Input Schema

Name	Required	Description
`tiers`	Yes
`weekend`	No	Non-business weekdays, 0=Sunday..6=Saturday. Default [0, 6]; use [5, 6] for a Friday/Saturday weekend.
`calendar`	No	Named holiday calendar with a source and supported date range (outside it the answer is unsupported), weekends-only (Saturday/Sunday only), or caller (only the holidays you list).
`currency`	Yes
`freeDays`	Yes
`holidays`	No	Extra non-business dates YYYY-MM-DD (company closures, a calendar we do not carry).
`receivedOn`	Yes
`releasedOn`	Yes
`freeCounting`	Yes
`chargeCounting`	Yes	Whether chargeable days skip weekends/holidays.
`receiptDayCounts`	Yes	Whether the day of receipt is day 1.
`releaseDayCounts`	Yes	Whether the release day is counted.
`claimedChargeMinor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the outputs (last free day, chargeable days, per-tier breakdown, total), which signals a pure computation rather than a mutation, but it never states that the tool is side-effect free, what happens when dates or the calendar range are invalid, or how the total is rounded into minor units. For a deterministic calculator that is an acceptable but thin behavioral profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The label-then-elaboration layout is front-loaded and readable, but the opening clause is restated almost verbatim in the second half, and the text is cut off mid-phrase ("the total in m"), which costs clarity. It is a single run-on sentence carrying several distinct ideas that would separate better.

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?

Given 13 parameters, moderate schema coverage and no output schema, the description does the important extra work of enumerating the return values so the agent knows what comes back. The main remaining holes are the purpose of claimedChargeMinor and the meaning of currency and holiday/weekend inputs, which are only partly inferable.

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?

With only 46% schema coverage across 13 parameters, the description meaningfully compensates: it explains the receipt-day and release-day counting flags, free-day counting on calendar versus business days against a named or caller calendar, and the tier schedule keyed by chargeable day number. It leaves currency, claimedChargeMinor, holidays and weekend entirely to the schema, so some gap remains, but the core required parameters gain real meaning.

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 uses a specific verb-and-resource framing ("Counts days between a received date and a released date") and names the domain explicitly: storage, demurrage, detention or parking charges, returning free-time end date, chargeable days and tiered amount. An agent can tell what it computes without opening the schema. It does not, however, distinguish itself from plausible siblings such as business-deadline or booking-change-penalty.

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 by the domain framing — you use it when you have a received date, a released date and a rate schedule. There is no explicit when-to-use versus when-not-to-use statement, no prerequisite conditions, and no named alternative for the closely related day-counting or penalty tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All WritersLogic business agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?