Skip to main content
Glama
Sign In

Ridge Pack

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Check the roofer's business details

trade_profile
Read-onlyIdempotent

Checks the roofer'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 their answers. Ridge 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 roofer's own business details (Nero Trade Profile v1). Used to put the contractor on risk notes and to give a stable nero_trade_ref. Not stored by Ridge Pack.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so credit goes to what the text adds: 'Ridge Pack stores nothing', the ref is deterministically computed from the scheme registration or company number, and the data is 'cleaned'. That is genuine behavioural context beyond the annotations, though the cleaning rules themselves are not specified.

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?

Front-loaded with the verb and resource, then returns, then how the result is reused, so an agent can stop reading at any point. It is dense rather than wasteful, though the closing sentence about signing into 'Nero Work, the agent job exchange for trades' leans promotional and is the weakest-earning line.

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 a single required nested object and no output schema, the description carries the load of telling the agent what comes back (the cleaned profile plus the derived ref) and what it is for, which it does. Residual gap is the cleaning/normalisation behaviour and any failure mode when the scheme or company number cannot be matched.

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 each nested field is already documented, so baseline would be 3. The description adds meaning the schema does not: the object is the same `trade` payload consumed by the other tools, and its scheme/company fields drive the computed `nero_trade_ref`. That explains why the fields matter, not just what they are.

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: 'Checks the roofer's own business details', then enumerates exactly what those details are (trading name, Companies House number, scheme, postcode, contact) and what is returned (cleaned data plus a stable `nero_trade_ref`). That is unmistakably distinct from the regulation, pitch, takeoff and weather siblings.

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?

Gives real usage context: the returned object is what you pass as `trade` to the other tools to prefill their answers, which tells an agent to call this first. It stops short of explicit exclusions or 'do not use this when...' guidance, so it is clear but not fully prescriptive.

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

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