Skip to main content
Glama

booking-change-penalty

Which cancellation or change tier applies at this moment, and what does it cost? — Given a booking start, the moment of change, the booking amount and a tiered policy whose deadlines are either elapsed hours before start ('48 hours') or local calendar days at a local time ('18:00 the day before' in the venue's zone, DST-correct), returns the applicable tier, its deadline instants, the penalty in minor units under your stated rounding, and when the next tier begins; checks an ass

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": {
      "startAt": "<startAt>",
      "changeAt": "<changeAt>",
      "amountMinor": "<amountMinor>",
      "currency": "<currency>",
      "tiers": "<tiers>",
      "rounding": "<rounding>"
    },
    "name": "booking-change-penalty"
  }
}

Input Schema

NameRequiredDescriptionDefault
tiersYes
startAtYes
changeAtYesThe moment of cancellation/change; never read from the clock.
currencyYes
roundingYesApplied to percentage penalties.
timeZoneNoNeeded for daysBefore tiers.
noShowTierNoTier name charged when changeAt is after startAt; default the most severe tier.
amountMinorYes
claimedPenaltyMinorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 substantial work: it discloses that tier deadlines may be hour-based or local-calendar-day based, that day-based evaluation is DST-correct in the venue's zone, that rounding is applied per the caller's stated mode, and that deadline instants and the next-tier boundary are returned. It does not cover failure behavior (e.g. when no tier matches) and the final clause ('checks an ass…') is truncated, leaving a promised validation behavior unspecified.

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 front-loaded question is a strong lead, but the body collapses into a single long run-on sentence dense with parentheticals, and it terminates mid-word ('checks an ass'), which reads as an unfinished fragment rather than a deliberate close. The content mostly earns its place; the packaging does not.

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

Completeness3/5

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

For a 9-parameter, 6-required computation with no output schema, the description does well on outputs (tier, deadline instants, penalty, next-tier start) and on the time semantics that make the tool non-obvious. It falls short on edge behavior — no matching tier, invalid policy with both or neither of hoursBefore/daysBefore, and the no-show case — and the truncated final clause leaves the claimedPenaltyMinor check undefined.

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 coverage is 44% across 9 parameters, so the description must compensate and it does partially: it clarifies the two deadline idioms ('48 hours' elapsed hours vs '18:00 the day before' in the venue's zone) and that the penalty is expressed in minor units under the caller's rounding. However, it says nothing about noShowTier, timeZone selection, or claimedPenaltyMinor, and the truncated tail likely referred to the latter, so several parameters remain explained only by terse schema text or not at all.

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?

The opening question states a specific computation over a specific resource: which cancellation/change tier applies and what it costs, given booking start, change moment, amount and a tiered policy. The description also enumerates the returned artifacts (tier, deadline instants, penalty in minor units, next-tier start), so an agent knows exactly what this does without opening the schema.

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 implied by the input list ('Given a booking start, the moment of change, the booking amount and a tiered policy'), which tells an agent when the tool is applicable, but there is no explicit when-not guidance, no prerequisite statements, and no named alternative for related questions such as plain date arithmetic or fee rounding.

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