Supplier Invoice Tool

Create the business invoice book

create_trade_account

Start here, once per business. Creates the trade's invoice book and returns an API key to send as "Authorization: Bearer " on every other call. Test mode: free, nothing is charged. The same identity (company number) can later sign the trade into Nero Work without a new sign up.

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": {
      "name": "<name>"
    },
    "name": "create_trade_account"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Trading name, for example Spark & Sons Electrical Ltd.
`vat_number`	No
`company_number`	No	Companies House number, if a limited company. Leave out for a sole trader.
`vat_registered`	No	Default true. If false, bills are entered gross with no VAT.
`job_reference_style`	No	"number" (recommended when jobs are numbered): JOB-1042, Job 1042 and 1042 are all job 1042. "prefixed": keep JOB-1042 as written.
`job_reference_prefixes`	No	Letters the trade puts before job numbers on orders, for example ["JOB", "HAUS"]. Default JOB, NW, REF.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already flag readOnlyHint=false, destructiveHint=false and idempotentHint=false; the description adds real context beyond them: the tool yields a bearer token required by all other calls, and test mode is free with nothing charged. It stops short of describing what happens on a second call for the same company or what errors look like.

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-loads the critical 'Start here, once per business' instruction and keeps each following sentence to one useful fact (key, cost, identity). The Nero Work sentence is slightly tangential but justifies its place by explaining the persistence of company_number.

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

Completeness3/5

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

Covers the entry-point role, authentication outcome, and cost, which is most of what an agent needs. With no output schema and six parameters, gaps remain around return payload shape (beyond the key) and behavior on repeated calls for the same business.

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 83%, so the schema already carries most parameter meaning. The description still adds value by explaining that company_number acts as a durable identity reusable for signing into Nero Work later, which is not stated in the schema.

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 ('Creates the trade's invoice book') plus the key side effect ('returns an API key'). 'Start here, once per business' immediately distinguishes it from every sibling such as get_account or update_settings, which cannot be the first call.

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 explicit ordering and frequency guidance ('Start here, once per business') and explains the follow-on usage of the returned key on every other call. It does not name an alternative or state exclusions, but for a bootstrap tool the when-to-use instruction is clear and unambiguous.

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

All Supplier Invoice Tool tools Inspect

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.