Skip to main content
Glama
Sign In

Spark Pack

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Check the electrician's business details

trade_profile
Read-onlyIdempotent

Checks the electrician's own business details (Nero Trade Profile v1: trading name, Companies House number, competent person scheme and number, postcode, contact) and returns them cleaned, with a stable nero_trade_ref computed from the scheme registration or company number. The same object, given as trade to the other tools, prefills certificates and grid forms. Spark 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 electrician's own business details (Nero Trade Profile v1). Used to prefill certificate contractor fields and to give a stable nero_trade_ref. Not stored by Spark Pack.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 genuinely new behavior: the returned object is normalized ('cleaned'), the reference is deterministically derived from scheme registration or company number, and 'Spark Pack stores nothing' confirms no persistence side effect. The closing line about later signing into Nero Work is context rather than call-time behavior.

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

Conciseness3/5

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

The core is front-loaded in a single dense sentence, which is good, but the final sentence about signing the business into Nero Work is promotional context that does not help an agent decide or invoke correctly. Three sentences for one parameter is slightly over-built.

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 no output schema, the description correctly steps in to describe the return shape (cleaned business details plus a stable reference) and the ref's derivation source. Given a single nested object parameter and strong annotations, little is missing beyond the required-vs-optional ambiguity.

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% with per-field descriptions, so the baseline is 3; the description earns above it because it explains the consequence of the inputs — which fields drive the computed `nero_trade_ref` (scheme registration or company number) and that the object is reusable across other tools. One flaw: the nested text calls `trade` 'Optional' while the schema marks it required, which is a real inconsistency the description does not resolve.

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 and resource: it checks the electrician's own business details and returns them cleaned with a computed `nero_trade_ref`. It also implicitly separates itself from the check_*/get_certificate_schema siblings by framing this as the profile that other tools consume as `trade`. It stops short of naming a sibling it might be confused with, which keeps it out of the top band.

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 same object, given as `trade` to the other tools, prefills certificates and grid forms' tells the agent this is the prefill source, but there is no explicit 'call this before X' instruction and no when-not guidance.

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

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