Skip to main content
Glama
Sign In

Spark Pack

by io.github.Nero-Engine
OverviewDiscussionsAdmin

Certificate fields as a JSON schema

get_certificate_schema
Read-onlyIdempotent

Returns the fields an Electrical Installation Certificate (eic), Minor Electrical Installation Works Certificate (minor_works) or Electrical Installation Condition Report (eicr) needs, as a JSON Schema the assistant fills from the job notes and test readings (spark-pack-certs-1.0 (for BS 7671:2018+A4:2026 certificates)). Includes which certificate to use when, and the contractor block prefilled from trade if given. check_certificate checks the filled object. Field names are Spark Pack's own; the electrician transfers the values to the official form in their scheme portal or software.

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

Input Schema

NameRequiredDescriptionDefault
tradeNoOptional. 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.
certificateYeseic for new circuits, consumer units and new installations; minor_works for additions or alterations to one existing circuit; eicr for periodic inspection reports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower; the description adds real context: the schema version (spark-pack-certs-1.0 for BS 7671:2018+A4:2026), that the trade profile is not stored by Spark Pack, that field names are Spark Pack's own, and that values are transferred manually to the official form. This is meaningful behavior beyond the annotations.

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?

Content is front-loaded with the purpose, followed by workflow and caveats. The nested parenthetical version string and the mid-sentence jump to check_certificate make it slightly harder to scan than it needs to be, but no sentence is wasted.

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?

For a two-parameter tool with a nested trade object and no output schema, the description covers what is returned (a JSON Schema), how it is meant to be consumed, versioning, and the downstream check step. The only gap is that it does not describe the shape or scale of the returned schema.

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 description coverage is 100%, so both parameters are already fully documented, including the enum meaning for `certificate`. The description only restates that the contractor block is prefilled from `trade` when given, which the schema already says; it adds little new meaning.

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 — returns the required fields for eic, minor_works and eicr as a JSON Schema — and names the enum values explicitly. It is clearly distinguishable from check_certificate, which it identifies as the validator of the filled object.

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 establishes the workflow (get the schema, fill it from job notes and test readings, then run check_certificate) and says the returned schema includes guidance on which certificate to use when. It does not spell out an explicit 'use this instead of X when Y' exclusion, but the sequencing with check_certificate is unambiguous.

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