Skip to main content
Glama
Sign In

Nero Reviews: verified job reviews for trades

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Set up the business for reviews

register_trade

Sets up a tradesperson's business once, with their name, colours, logo and optional Google review link. Returns a trade_key (every other tool needs it, and it is shown only once), the public trade page link, and a nero_trade_ref that carries the history into Nero Work. No human sign-up form or password exists; this call is the sign-up. One registration per business; details change through update_trade.

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": {
      "display_name": "<display_name>"
    },
    "name": "register_trade"
  }
}

Input Schema

NameRequiredDescriptionDefault
townNoTown or area served, for example "Leeds".
logo_urlNohttps link to the logo image (square works best). Without one, the initials are shown.
trade_typeNoShort trade label shown on the pages, for example "Electrician" or "Plumbing & heating".
display_nameYesTrading name customers know, for example "Brightwire Electrical".
licence_bodyNoOptional. Competent person scheme or licence body, for example "niceic" or "napit". With licence_number it gives the nero_trade_ref.
company_numberNoOptional. UK Companies House number. Gives a stable nero_trade_ref, the same one Spark Pack and Nero Work use.
licence_numberNoOptional. Scheme registration number.
primary_colourNoMain brand colour as hex, for example "#1F3A5F". Used for the page header and buttons. Text colour on it is picked automatically for contrast.
secondary_colourNoAccent colour as hex, used for the level badge and the logo placeholder.
google_review_urlNoOptional. The business's Google "write a review" link (g.page/r/..., maps.app.goo.gl or google.com). If set, EVERY reviewer is offered it after sending their stars, whatever they gave.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say non-read-only, non-idempotent and non-destructive; the description adds crucial context beyond that: the trade_key is shown only once and is required by every other tool, an nero_trade_ref is produced for history carry-over, and there is no password-based account. These are exactly the operational facts an agent needs before invoking an irreversible one-time setup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action and immediately followed by the one-time key warning and the alternative tool. Nothing is redundant given the stakes of a single-shot registration.

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?

Covers a 10-parameter creation tool with no output schema by describing the three return values (trade_key, public trade page link, nero_trade_ref) and their downstream significance. An agent knows what it gets back, what it must persist, and how the record is later modified.

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% and each field (town, logo_url, colours, licence fields, google_review_url) is already documented in the schema. The description's mention of name, colours, logo and review link merely restates that set and adds no format or interaction detail beyond it, so the baseline 3 applies.

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 ('Sets up a tradesperson's business once') plus the fields it accepts, and explicitly contrasts itself with the sibling update_trade. An agent can distinguish it from update_trade without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use context ('this call is the sign-up', 'No human sign-up form or password exists') and an explicit alternative for the change case ('details change through update_trade'). The 'one registration per business' constraint further rules out repeat calls.

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

All Nero Reviews: verified job reviews for trades 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