Skip to main content
Glama
Sign In

Nero Reviews: verified job reviews for trades

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Change the business details on review pages

update_trade
Idempotent

Changes the business details shown on the review pages: name, trade, town, brand colours, logo link or Google review link. Only the fields given change. Returns the trade page link.

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": {
      "trade_key": "<trade_key>"
    },
    "name": "update_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_keyYesThe trade_key that register_trade returned for this business (starts with nrk_).
trade_typeNoShort trade label shown on the pages, for example "Electrician" or "Plumbing & heating".
display_nameNoTrading 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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that by confirming partial-update behaviour and by stating the return value (the trade page link), which matters because there is no output schema.

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 short sentences, front-loaded with the verb and affected fields, then the partial-update rule and the return value. Nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter mutation tool with no output schema, the description covers the essentials: what changes, that unspecified fields stay intact, and what comes back. Missing is failure behaviour (invalid hex, unknown trade_key) and permission requirements, though annotations cover reversibility and idempotency.

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 the parameter descriptions are rich (hex format, licence body pairing, the Google review URL caveat), so the schema carries the semantics. The description only restates the field list in prose, adding little beyond it, which is the baseline case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ("Changes") plus resource ("business details shown on the review pages") and an enumerated field list, so the agent knows exactly what it mutates. It stops short of naming a sibling to avoid, but no sibling (dispute_review, reply_to_review, register_trade) plausibly does profile edits, so confusion risk is low.

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?

"Only the fields given change" usefully signals partial-update semantics, which tells the agent it need not resend the whole profile. There is no explicit when-to-use/when-not guidance and no statement of prerequisites such as needing a trade_key from register_trade, which only the schema reveals.

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