Skip to main content
Glama
Sign In

The Cable Code

by io.github.exquad
OverviewDiscussionsAdmin

Cable end preparation for an LV, MV or HV design

cable_prep
Read-onlyIdempotent

Prepare the end of an LV, MV or HV power cable for its termination or joint. The answer (thecablecode.prep/v1): steps[], each cut with the design's own depth and the diameter left; the makers' cut-back lengths for this voltage and size (makers' published instructions, unnamed, seen typical; none for low voltage); lug (the lug family by conductor class and metal, its standards, the strip length rule); for MV, kits (the termination and joint kinds that fit, with ranges, length and sheds from makers' public catalogues, no maker named) and creepage (the outdoor termination's minimum creepage per pollution class a to e, IEC TS 60815-3, with corrections and sources); fittings (gland diameters and IEC 62444 anchorage, EN 50181 connector interfaces, the IEC 61914 cleat force and the standing sheath voltage of single cores); and the step sheet PDF with pdf: true. Send the cable as design_cable takes it (sentence, spec or design) and the site in input. Use design_cable for the cable itself and commissioning_sheet for the tests after installation; this tool is only the end preparation. Without full and without payment the answer is the verdict a visitor sees on the site, counted against the designs' daily free allowance; full: true (or any paid call) answers in full. A separate paid call at its own price; a bad request costs nothing. input: {pollution?: a | b | c | d | e (the site pollution severity class of IEC TS 60815-1 for the outdoor termination's minimum creepage; absent: every class, none picked), edge?: true (the class read at its upper edge on the IEC TS 60815-1 curve), htm_lower?: true (an HTM insulator: one class lower), fittings?: {formation: trefoil | flat, spacingMm, currentA, lengthM (single-point bonded section), limitV, ikKa, rx, ipKa, leadM, cleatM, freq: 50 | 60, connectorA} (every field optional)} (the design decides the rest, and the kit's own instruction wins over the makers' lengths). $0.50 per calculation in USDC with x402; the free verdict counts against the designs' 2 free calls per caller per UTC day; a list of up to 50 items at $0.50 per item, one payment.

Input Schema

NameRequiredDescriptionDefault
pdfNoFull mode: add the calculation sheet as pdf_base64.
fullNotrue: the whole answer, a paid call. Without it the free verdict, counted against the designs' daily free allowance.
langNoAny of the site's 15 languages; default en.
specNoInstead of a sentence: a spec as design_cable takes it.
inputNoinput: {pollution?: a | b | c | d | e (the site pollution severity class of IEC TS 60815-1 for the outdoor termination's minimum creepage; absent: every class, none picked), edge?: true (the class read at its upper edge on the IEC TS 60815-1 curve), htm_lower?: true (an HTM insulator: one class lower), fittings?: {formation: trefoil | flat, spacingMm, currentA, lengthM (single-point bonded section), limitV, ikKa, rx, ipKa, leadM, cleatM, freq: 50 | 60, connectorA} (every field optional)} (the design decides the rest, and the kit's own instruction wins over the makers' lengths)
itemsNoInstead of one: a project's list, 1 to 50 items, each {sentence | spec | design, input}; always in full, paid per item.
designNoInstead of a sentence: the design field of a design_cable answer.
sentenceNoThe cable in words or its designation, as design_cable takes it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / input / description
      Previous value: -"input: {pollution?: a | b | c | d | e} (the site pollution severity class of IEC TS 60815-1 for the outdoor termination's minimum creepage; absent: every class, none picked; the design decides the rest, and the kit's own instruction wins over the makers' lengths)"New value: +"input: {pollution?: a | b | c | d | e (the site pollution severity class of IEC TS 60815-1 for the outdoor termination's minimum creepage; absent: every class, none picked), edge?: true (the class read at its upper edge on the IEC TS 60815-1 curve), htm_lower?: true (an HTM insulator: one class lower), fittings?: {formation: trefoil | flat, spacingMm, currentA, lengthM (single-point bonded section), limitV, ikKa, rx, ipKa, leadM, cleatM, freq: 50 | 60, connectorA} (every field optional)} (the design decides the rest, and the kit's own instruction wins over the makers' lengths)"
  2. Changed1 schema field changed
    • changedInput schema / properties / input / description
      Previous value: -"input: none (the design decides; the kit's own instruction wins over the makers' lengths)"New value: +"input: {pollution?: a | b | c | d | e} (the site pollution severity class of IEC TS 60815-1 for the outdoor termination's minimum creepage; absent: every class, none picked; the design decides the rest, and the kit's own instruction wins over the makers' lengths)"
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses pricing ($0.50 per calculation in USDC via x402), the free verdict counted against 2 free calls per caller per UTC day, that a bad request costs nothing, and the 50-item batch pricing. This is substantial behavioral context an agent needs before invoking.

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?

Purpose is front-loaded, but the answer description is a dense run-on wall of text mixing return structure, pricing, and input semantics. It is information-rich but hard to parse, and some clauses could be split or trimmed.

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

Completeness5/5

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

For a complex, no-output-schema tool, the description thoroughly enumerates the return structure (steps, cut-back lengths, lug, kits, creepage, fittings, PDF) and the input contract. Nothing an agent needs to call it correctly appears missing.

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%, so the baseline is 3, but the description adds real meaning: it explains the pollution classes, edge/htm_lower semantics, the fittings sub-fields, and the governing rule that 'the design decides the rest, and the kit's own instruction wins over the makers' lengths.' That interaction logic is not 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 ('Prepare the end of an LV, MV or HV power cable for its termination or joint') and explicitly distinguishes itself from design_cable and commissioning_sheet. An agent can tell exactly what this tool does and does not do.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'Use design_cable for the cable itself and commissioning_sheet for the tests after installation; this tool is only the end preparation.' It also states the free-vs-paid condition and that a bad request costs nothing, leaving little to inference.

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

All The Cable Code 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