Skip to main content
Glama

Payment & Cancellation Timeline Builder

payment-timeline-builder
Read-onlyIdempotent

Builds a dated payment and cancellation timeline for a trip: deposit, optional instalments and balance (with client due dates set a buffer ahead of the supplier deadlines) and the cancellation charge that applies on each date. Default terms are examples only; pass the terms from the supplier contract. Web page: https://globalluxagency.com/tools/payment-timeline-builder

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": {
      "departureDate": "<departureDate>",
      "total": "<total>"
    },
    "name": "payment-timeline-builder"
  }
}

Input Schema

NameRequiredDescriptionDefault
todayNoReference date for flagging deadlines that have passed, YYYY-MM-DD. Defaults to today (UTC).
totalYesTotal cost of the booking.
currencyNoCurrency of the amounts.GBP
bookingDateNoBooking date, YYYY-MM-DD. Defaults to today (UTC).
depositTypeNoWhether depositValue is a percentage of the total or a fixed amount.percent
instalmentsNoOptional extra instalments as "daysBefore:percent" pairs, e.g. "120:25" (up to 6).
cancellationNoCancellation tiers as "daysBefore:percentForfeited" pairs (up to 8), e.g. "84:25,56:50,29:75,0:100".84:25,56:50,29:75,0:100
depositValueNoDeposit due at booking (percent or amount; example default 25%).
departureDateYesDeparture (or service start) date, YYYY-MM-DD.
clientBufferDaysNoAsk the client this many days before each supplier deadline.
balanceDaysBeforeNoBalance due this many days before departure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely useful behavioral detail: client-facing due dates are deliberately set a buffer ahead of supplier deadlines, and cancellation charges are computed per date, plus the warning that defaults are illustrative. It does not explain the shape of the returned timeline, which is a modest gap given there is no output schema.

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?

Two front-loaded sentences plus a documentation link; the core purpose and the default-terms caveat both appear before any ancillary information. The trailing web page URL is the only element that does not directly help an agent invoke the tool.

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 an 11-parameter tool with no output schema, the description covers purpose, the key semantic quirk (buffer-shifted client dates), the cancellation-per-date output, and the misuse risk around example defaults. Absent a full return-value explanation, this is still sufficient for an agent to call it correctly.

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 coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the relationship the schema only implies — that client dates are shifted a buffer ahead of supplier deadlines (clarifying clientBufferDays) and that the cancellation/instalment defaults are examples rather than policy. It still does not illustrate the "daysBefore:percent" pair syntax in prose, leaving that to the schema patterns.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ("Builds a dated payment and cancellation timeline for a trip") and enumerates the exact artifacts produced: deposit, optional instalments, balance, and the cancellation charge applicable on each date. This is clearly distinct from the sibling *-calculator tools, which price scenarios rather than generating a dated schedule.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear usage directive — "Default terms are examples only; pass the terms from the supplier contract" — which tells the agent not to rely on built-in defaults for cancellation/instalment tiers. It lacks an explicit when-to-use vs. sibling-alternative comparison, but the scope (trip booking with supplier contract terms) is unambiguous.

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