Skip to main content
Glama
Sign In

Flow Pack

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Is this work notifiable, and who can do it?

check_notifiable_work
Read-onlyIdempotent

For plumbing and heating jobs in England or Wales: does it need a Gas Safe registered engineer, an unvented (G3) qualified installer, building regulations notification (Approved Documents G, J, L and others) and a water company notice (Water Fittings Regulations, regulation 5)? Returns, per job, who can do it, the self-certification route (competent person scheme within 30 days, or building control before starting) and what to do next, including CO alarm and Boiler Plus rules. Typical call: {"nation":"england","work":["gas_boiler_replacement","unvented_cylinder_new"]}.

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": "check_notifiable_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
workYesOne or more jobs.
tradeNoOptional. The plumber or heating engineer's own business details (Nero Trade Profile v1, the same shape as Spark Pack and Nero Work). Used to prefill records and to give a stable nero_trade_ref. Not stored by Flow Pack.
nationNoDefault england.
water_approved_contractorNoTrue if the installer is a water approved contractor (for example WaterSafe).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing what is returned per job (who can do it, the self-certification route, CO alarm and Boiler Plus rules), but says nothing about cost, limits, or failure modes when a job type is unsupported.

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?

The jurisdiction and work-type scoping is front-loaded and the return summary follows logically. The single dense block with nested parentheticals (Approved Documents G, J, L; reg 5) is slightly run-on but every clause carries substantive scope information.

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?

With no output schema, the description does describe the shape of the answer (per-job verdict, competent person route within 30 days or building control before starting, next steps), which is the key gap it needed to fill. However, it leaves unclear how the optional trade object influences the returned advice and what happens with unsupported or out-of-scope work types.

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%, so all four parameters are already documented, and the description adds only a concrete example call showing nation plus a two-item work array. It does not explain how trade details affect the answer or why the licence_body enum should be set to gas_safe for gas work.

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 specific question (is this work notifiable, and who can do it) and the exact domain (plumbing and heating jobs in England or Wales), enumerating the regimes it evaluates: Gas Safe, unvented G3, building regulations notification, and water company notice. That is specific enough to separate it from siblings like check_gas_record or the sizing tools without opening a 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?

Scope is explicit ('for plumbing and heating jobs in England or Wales') and a typical call is supplied, so an agent knows the intended invocation. There is no explicit when-not-to-use clause or named alternative among the siblings, 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.

All Flow 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