Skip to main content
Glama
Sign In

Brush Pack

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Check the decorator's business details

trade_profile
Read-onlyIdempotent

Checks the decorator's own business details (Nero Trade Profile v1: trading name, Companies House number, trade body and number such as PDA or TrustMark, postcode, contact) and returns them cleaned, with a stable nero_trade_ref computed from the trade body membership or company number. The same object, given as trade to the other tools, prefills their answers. Brush Pack stores nothing. The same profile and reference can later be used to sign the business into Nero Work, the agent job exchange for trades.

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": "<trade>"
    },
    "name": "trade_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
tradeYesOptional. The decorator's own business details (Nero Trade Profile v1). Used to prefill quotes and to give a stable nero_trade_ref. Not stored by Brush Pack.

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: results are 'cleaned', the `nero_trade_ref` is stable and derived deterministically from trade body membership or company number, and 'Brush Pack stores nothing' settles the persistence question. It stops short of saying what happens with malformed or missing details.

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?

Purpose and enumerations are front-loaded, followed by return behavior, then parameter reuse and storage. No sentence is redundant for calling the tool. The closing sentence about signing into Nero Work is promotional context that does not help an agent decide or invoke, which is the only waste.

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?

With readOnly/idempotent annotations, a fully described nested schema and no output schema, the description carries the remaining burden well: it covers what flows in, what comes out, that nothing is stored, and where the object is reused. The main residual gap is failure behavior — whether inconsistent company number and licence body combinations are rejected or normalized.

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 coverage is 100% and the single `trade` object is fully documented field by field, so the baseline is 3. The description goes beyond the schema by framing the object as a portable 'Nero Trade Profile v1' that can be passed as `trade` to the other tools to prefill them and to derive the stable reference — that is real semantic value, not restatement.

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?

The description names a specific resource (the decorator's own business details, 'Nero Trade Profile v1') and enumerates exactly which fields it covers: trading name, Companies House number, trade body and number, postcode, contact. It also states what comes back (cleaned details plus a stable `nero_trade_ref`). The verb 'checks' is slightly ambiguous — it could mean validate or retrieve — which keeps it off a 5, but no sibling tool overlaps this domain.

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?

Usage is implied rather than stated: the description explains that the returned object, passed as `trade` to the other tools, prefills their answers, which hints this should be called early. However, it never explicitly says when to call this versus skipping it, what happens without a profile, or any exclusions. The downstream Nero Work mention is informational, not selection guidance.

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

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