Skip to main content
Glama
Sign In

Ridge Pack

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Weather window for roof work

weather_window
Read-onlyIdempotent

Gets the hourly forecast for a UK postcode (today and up to 8 days ahead, from MET Norway) and checks each working hour against wind, gusts, rain, frost and the material's limits for the job type (tiling, membranes and sheets, torch-on, liquid coatings, EPDM adhesive, mortar bedding, lead work, inspection). Returns each day as good, caution or no_go with good hours, the best window, max gust in mph and the reasons, plus the limits used. Limits are Ridge Pack's cautious defaults (HSE sets no single wind speed) and can be overridden. Typical call: {"postcode":"BS1 4DJ","job_type":"membrane_or_sheets","start_date":"2026-11-16","end_date":"2026-11-20"}.

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": {
      "postcode": "<postcode>"
    },
    "name": "weather_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
tradeNoOptional. The roofer's own business details (Nero Trade Profile v1). Used to put the contractor on risk notes and to give a stable nero_trade_ref. Not stored by Ridge Pack.
limitsNoOptional overrides.
end_dateNoLast day, YYYY-MM-DD, at most 8 days after today. Default start + 6 days.
end_hourNoEnd of the working day, 1 to 23. Default 17.
job_typeNoWhat is being done. Default tiling_slating.
postcodeYesFull UK postcode of the job.
start_dateNoFirst day, YYYY-MM-DD. Default today.
start_hourNoStart of the working day, 0 to 22 (UK time). Default 8.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds substantive behavior beyond that: the forecast source and horizon, the per-day verdict scale (good/caution/no_go), what accompanies each verdict (good hours, best window, max gust, reasons, limits used), and that limits are Ridge Pack's cautious defaults rather than a regulatory single wind speed and are overridable.

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 outcome, and the trailing example call is genuinely useful for invocation. It is a single dense, run-on block though; the verdict format, limit policy and example would scan faster as separate sentences or bullets.

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 8 parameters including a nested trade object and no output schema, the description compensates by describing the return shape in detail (verdicts, good hours, best window, max gust, reasons, limits used). Nothing an agent needs to call it correctly or interpret the result 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 description coverage is 100%, so parameter documentation is essentially complete and the baseline of 3 applies. The description adds framing beyond the schema — that limits reflect cautious defaults and can be overridden, and the 8-day horizon — plus a worked example that shows how postcode, job_type and date range combine in practice.

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?

Specific verb plus resource: fetches hourly forecast for a UK postcode and checks each working hour against wind, gusts, rain, frost and material limits, returning a per-day good/caution/no_go verdict. It names the data source (MET Norway) and the job types supported, so an agent can distinguish it from siblings like roof_takeoff or storm_triage 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 Guidelines4/5

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

The description gives clear context for use — planning working hours for a job type at a postcode across a date range — and supplies a concrete typical call, which anchors invocation. It does not state when to prefer an alternative (e.g. storm_triage for post-storm damage decisions) or any exclusions, so it stays short of full 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.

All Ridge Pack toolsInspect
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.

Resources