Skip to main content
Glama
Sign In

Nero Reviews: verified job reviews for trades

by io.github.Nero-Engine
OverviewDiscussionsAdmin

List every review, newest first

list_reviews
Read-onlyIdempotent

Lists every review for the business, newest first (the only order offered; reviews are never sorted by stars), with stars, words, reviewer, job, date and any reply. Use limit and offset to page through.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return. Default 20.
offsetNoHow many newest reviews to skip. Use next_offset from the last call.
trade_keyYesThe trade_key that register_trade returned for this business (starts with nrk_).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description goes beyond that by disclosing the sort invariant (never sorted by stars), the exact result fields returned, and the pagination contract — exactly the behavioral context an agent needs.

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?

Two sentences, front-loaded with purpose and ordering before pagination mechanics; no filler. The parenthetical about sorting is slightly defensive but earns its place by preventing a wrong assumption.

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?

There is no output schema, so the description carries the return-value burden — and it does, naming stars, words, reviewer, job, date, and replies. Combined with the ordering and paging rules, nothing essential is missing for a simple read-only list tool.

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 coverage is 100%, so the schema already documents limit, offset, and trade_key in comparable detail, including the next_offset hint. The description's paging sentence reinforces but does not materially extend that meaning, 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?

The description opens with a specific verb and resource ("Lists every review for the business"), states the ordering, and enumerates the returned fields. An agent can immediately tell this apart from siblings like dispute_review or reply_to_review, which mutate rather than list.

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?

It gives concrete operational guidance for paging ("Use limit and offset to page through") and forecloses a false expectation by noting newest-first is the only order offered. It stops short of naming when to prefer a sibling tool, but no exclusion is needed given the narrow purpose.

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