@splice-cad/mcp

Official

by splice-cad

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

search_cables

Search the cable parts database to find specific cables, such as '4 core shielded 20 awg', for use in BOM entries.

Instructions

Search the Splice cable parts database. Only use when the user asks to find a cable in the database. For most cases, create cable BOM entries directly. Supports "4 core shielded 20 awg", "belden 2 conductor".

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

Input Schema

Name	Required	Description
`limit`	No	Max results
`query`	Yes	Search query (e.g. "4 core shielded 20 awg")
`offset`	No	Pagination offset

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Aug 2, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Search' and gives examples, but does not mention that this is a read-only operation, how results are returned, or any potential limitations. This is a sparse disclosure for a tool with no annotation safety hints.

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 two sentences, front-loaded with purpose, and includes practical examples and usage guidance. Every sentence earns its place with no fluff.

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?

For a simple search tool with 3 parameters and no output schema, the description is adequate but not complete. It does not describe the return format or result structure, relying on the 'search' verb and schema to imply behavior. It's sufficient for basic use but lacks detail for a fully autonomous agent.

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 baseline is 3. The description adds a second query example ('belden 2 conductor') beyond the schema's example, but does not explain limit or offset semantics beyond what the schema already provides. This contributes marginal value.

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 tool's function as searching the Splice cable parts database. It distinguishes from siblings like search_connectors and search_wires by specifying 'cable' and provides concrete examples of supported queries, making the purpose unambiguous.

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 explicitly says to use this tool only when the user asks to find a cable, and for most cases to create cable BOM entries directly. This gives clear when-to-use and when-not-to-use guidance, though it doesn't name specific sibling tools as alternatives.

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