Skip to main content
Glama

Work out the deadlines on a notice

calculate_deadlines
Read-onlyIdempotent

Work out the time limits the law sets in England for a parking or traffic notice from the dates printed on it: the reduced-amount period, formal representations, when a council's Notice to Owner may come and the latest it may come, the tribunal, POPLA or IAS after a rejection, and whether a private Notice to Keeper came too late for the keeper to be liable. Each date errs early and comes with its legal source. The notice itself is authoritative.

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": {
      "notice_type": "<notice_type>",
      "notice_date": "<notice_date>"
    },
    "name": "calculate_deadlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_dateNoThe date of the parking or contravention, yyyy-mm-dd. Needed to check a private Notice to Keeper's timing.
notice_dateYesThe date printed on the first notice (the PCN, the private Notice to Keeper, or the ticket on the car), yyyy-mm-dd.
notice_typeYescouncil_pcn_on_vehicle: a council PCN put on the car or handed over. council_parking_pcn_by_post: a council parking PCN sent by post from camera evidence. council_bus_lane_or_moving_traffic: a bus lane, box junction, banned turn or similar PCN sent by post. private_no_ticket_on_vehicle: a private company's Notice to Keeper sent by post, no ticket on the car. private_ticket_on_vehicle: a private company's ticket left on the car.
rejection_dateNoThe date of the letter refusing the challenge, yyyy-mm-dd, if there is one.
notice_to_owner_dateNoA council Notice to Owner's printed date, yyyy-mm-dd, if one has come.
notice_to_keeper_dateNoAfter a private ticket on the car: the printed date of the Notice to Keeper that came by post, yyyy-mm-dd.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses non-obvious behavior: each computed date deliberately 'errs early', every date is returned with its legal source, and the notice itself is authoritative. That tells an agent both how conservative the output is and that it should be presented as advisory rather than definitive — exactly the kind of context annotations cannot carry.

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?

Front-loaded with the verb and scope, then a single dense enumeration of outputs, closed by the two caveats. The enumeration is long but each item earns its place by telling the agent what it will get back; only mild trimming would be possible.

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

Completeness5/5

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

With no output schema, the description still enumerates the returned deadline categories and notes they carry legal sources, and it flags the authoritative-source caveat. For a 6-parameter, 2-required computation tool with annotations already covering safety, an agent has everything needed to call and interpret it.

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 100%, including a full per-value explanation of the notice_type enum, so the schema already does the heavy lifting. The description adds only indirect meaning — 'dates printed on it' points at notice_date and the Notice to Keeper sentence hints at event_date — without adding format or conditional-requirement detail beyond the schema.

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?

States a specific verb ('work out') and a precisely scoped resource ('the time limits the law sets in England for a parking or traffic notice'), then enumerates the exact deadline families computed: reduced-amount period, formal representations, Notice to Owner window, tribunal, POPLA/IAS, and Notice to Keeper lateness. Nothing here overlaps with the sibling guide/contravention-code tools, so an agent can route correctly on name plus description alone.

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 clear triggering context: the input is a parking or traffic notice and the dates printed on it, in England. It does not name an alternative tool or state when not to use it, and it does not say what to do when dates are missing, so it stops short of explicit when/when-not guidance.

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.