Skip to main content
Glama
Sign In
@splice-cad/mcp

@splice-cad/mcp

Official
by splice-cad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_cable

Add a custom multi-conductor cable to the parts database when no existing match is found, returning a part ID for BOM use.

Instructions

Create a custom multi-conductor cable in the parts database. Use when a cable is not found via search — e.g. from a datasheet. Returns a part ID for BOM entries.

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": {
      "mpn": "<mpn>",
      "manufacturer": "<manufacturer>",
      "core_count": "<core_count>",
      "cores": "<cores>"
    },
    "name": "create_cable"
  }
}

Input Schema

NameRequiredDescriptionDefault
mpnYesManufacturer Part Number
coresYesCore specifications
shieldedNoHas overall shield
is_publicNoMake visible to other users
core_countYesNumber of conductors
descriptionNoCable description
manufacturerYesManufacturer name
datasheet_urlNoURL to datasheet PDF

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It mentions creating a record and returning a part ID, which communicates the primary side effect and output, but it does not address potential duplicates, permission requirements, or relationship between core_count and the cores array.

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

Conciseness5/5

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

The description is three sentences, front-loaded with the primary purpose, followed by usage context and return value. Every sentence adds value with no redundancy.

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?

The description provides the tool's purpose, usage condition, and return value, which is sufficient given the thorough parameter schema. However, the relationship between core_count and the cores array is not clarified, and there is no output schema, so a bit more detail on the expected consistency would improve completeness.

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 every parameter has a description. The tool description adds little beyond the schema, and specifically does not clarify that core_count should match the length of the cores array, which is a non-obvious semantic relationship.

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?

The description clearly states the action ('Create a custom multi-conductor cable'), the target resource ('parts database'), and distinguishes the tool from siblings by specifying it is for cables not found via search. This provides a specific verb and resource with a clear scope.

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?

The description gives explicit when-to-use guidance ('Use when a cable is not found via search') and implies the alternative of searching first. It does not explicitly name sibling tools like search_cables, but the context is clear.

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

Deploy Server

Other Tools