Site Pack

Party Wall Act notices and dates (England and Wales)

party_wall_notices

Read-onlyIdempotent

Works out which notice the Party Wall etc. Act 1996 needs (line of junction, section 1; party structure, sections 2 and 3; adjacent excavation within 3 m or 6 m, section 6), and the dates: from planned_start_date the latest day to send it by the chosen method (by hand, first or second class post, email if agreed), or from serve_date the day it counts as served and the earliest start; plus the neighbour's 14 day reply deadline, when a dispute is deemed to arise, and when the notice lapses (12 months). Uses England and Wales bank holidays to 2028. Returns notice, section, dates (each as YYYY-MM-DD plus plain words), step by step working, what the notice must say, warnings and sources. Example: cutting a steel beam into a party wall, work to start 1 March 2027, posted first class: {"work":"insert_beam_or_dpc_into_party_wall","planned_start_date":"2027-03-01","serve_method":"first_class_post"}.

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": {
      "work": "<work>"
    },
    "name": "party_wall_notices"
  }
}

Input Schema

Name	Required	Description
`work`	Yes
`trade`	No	Optional. The builder's own business details (Nero Trade Profile v1). Used to prefill the contractor details in notices and CDM answers and to give a stable nero_trade_ref. Not stored by Site Pack.
`nation`	No	Defaults to england. The Act applies in England and Wales only.
`serve_date`	No	YYYY-MM-DD: the day the notice was or will be handed over, posted or emailed.
`serve_method`	No	Defaults to first_class_post.
`adjoining_owners`	No	How many adjoining owners (each gets their own notice). Defaults to 1.
`excavation_depth_m`	No	Excavations: depth of your excavation or foundation below ground.
`planned_start_date`	No	YYYY-MM-DD. Give this or serve_date (or both, to check the start is late enough).
`neighbour_foundation_depth_m`	No	Excavations: depth of the neighbour's foundations, if known.
`distance_to_neighbour_building_m`	No	Excavations: horizontal distance from the excavation to the neighbour's building.
`neighbour_will_agree_earlier_start`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered; the description goes further by disclosing what is computed (served date, earliest start, 14-day reply deadline, dispute point, 12-month lapse), the bank-holiday coverage limit ('to 2028') and that outputs include working, warnings and sources.

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?

Purpose and legal scope are front-loaded in the first clause, followed by dates, return shape and an example, with no filler sentences; the single dense paragraph is long but nearly every clause carries information, though it could be broken into steps for readability.

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 an 11-parameter, nested-object tool with no output schema, the description compensates by enumerating the returned keys (notice, section, dates, working, warnings, sources) and noting the jurisdictional limit and date horizon, leaving nothing an agent needs to call it correctly unstated.

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 82%, so the schema carries most parameter meaning and a 3 would be baseline; the description still adds value by tying planned_start_date/serve_date to the two computation modes, spelling out the serving methods, and giving a concrete filled-in example that shows how work, planned_start_date and serve_method combine.

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 description names a precise verb and resource ('Works out which notice the Party Wall etc. Act 1996 needs') and enumerates the covered sections (line of junction s1, party structure ss2-3, excavation s6), so an agent can tell it apart from cdm_duties, check_building_regs and check_permitted_development without opening any 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?

It explains how to drive the computation from either planned_start_date or serve_date ('or both, to check the start is late enough'), which is useful operational guidance, but never states when to choose this tool over its siblings or when it is not applicable (for example outside England and Wales, which is only stated in the schema).

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

All Site Pack 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.