Skip to main content
Glama

RemedyBridge free tools for tenants

Pre-action protocol timetable

calculate_pre_action_protocol_timetable
Read-onlyIdempotent

Works out the timetable the Pre-Action Protocol for Housing Conditions Claims (England) sets after a tenant’s letter of claim: the letter is treated as received two days after its date, the landlord should reply within 20 working days of that (paras 6.2 and 7.2(a)), the inspection should follow within 20 working days of the reply (para 7.4(a)), the expert’s report or agreed schedule within 10 working days of the inspection (para 7.4(b) and (d)), and the landlord’s full response within 20 working days of receiving it (para 6.3). Give the later dates as they happen to see each next date and whether each step was on time. It counts working days, leaving out weekends and bank holidays in England and Wales. The protocol calls these long stops, and they can be changed by agreement (para 9). Wales has its own protocol, with the same periods for the reply, the inspection and the report.

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": {
      "letterDate": "<letterDate>"
    },
    "name": "calculate_pre_action_protocol_timetable"
  }
}

Input Schema

NameRequiredDescriptionDefault
asAtNoWork it out as at this date instead of today in England (YYYY-MM-DD).
replyDateNoThe day the landlord replied to the letter of claim, if it has (YYYY-MM-DD).
letterDateYesThe date written on the letter of claim, not the day the landlord got it (YYYY-MM-DD).
inspectionDateNoThe day the property was inspected (by a single joint expert, or at a joint inspection), if it has been. Needs replyDate (YYYY-MM-DD).
reportReceivedDateNoThe day the expert’s report or the agreed schedule arrived, if it has. Needs inspectionDate (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial non-obvious behavior: deemed receipt two days after the letter date, working-day counting that excludes weekends and England/Wales bank holidays, and that long stops can be varied by agreement. It only gestures at the return shape ('each next date and whether each step was on time') rather than describing it, which with no output schema keeps it from a 5.

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 purpose, then the step sequence, then usage advice and jurisdiction caveats. The long enumeration of statutory paragraphs (6.2, 7.2(a), 7.4(a), 7.4(b) and (d), 6.3) is dense and mostly citation detail an agent does not need in order to call the tool, which costs a point.

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?

For a one-required-parameter, deterministic date calculator with no output schema, the description supplies everything needed: the governing rules, the working-day/bank-holiday convention, the incremental-date usage model, and the England versus Wales distinction. Nothing essential to correct invocation is missing.

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 baseline is 3, but the description adds derivation semantics beyond the schema: the letter date is treated as received two days after its date, and each subsequent deadline is measured from the prior supplied date. That meaningfully expands what the parameters imply.

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 and resource: computes the Pre-Action Protocol for Housing Conditions Claims (England) timetable. It is clearly distinguished from siblings like check_awaabs_law_deadlines and calculate_landlord_complaint_deadlines by naming the exact protocol, jurisdiction, and the sequence of steps it derives.

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 practical usage guidance: 'Give the later dates as they happen to see each next date and whether each step was on time,' which tells the agent to supply replyDate/inspectionDate/reportReceivedDate progressively. It also notes the Wales variant has its own protocol. It does not explicitly name an alternative sibling and when to prefer it, so it stops short of a 5.

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