Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

library_search

Read-onlyIdempotent

Search the device catalog, including built-in typical devices and imported vendor models, by query and device kind to find components for electrical documentation.

Instructions

Search the device catalog (built-in typical devices + your imported vendor models).

Example queries: 'S7-1200', 'balluff hub', 'mcb 2p', 'psu 24'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "library_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context that results come from a combined built-in plus imported-model catalog, but says nothing about matching behavior, result ordering, or how the 40-item default limit truncates results.

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?

Two short sentences, front-loaded with the core purpose, followed by illustrative queries that are cheap and concrete. Nothing is redundant, though the examples could have been paired with a hint about how they match.

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?

An output schema exists, so return values need no explanation, and annotations cover the read-only/idempotent profile. For a three-parameter search tool the remaining gap is small: it does not say whether kind and query combine as AND filters or how limit interacts with results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters. The example queries give some sense of what 'query' accepts (model names, product types), but 'kind' is not explained as a device-category filter beyond the bare enum, and 'limit' (default 40) is never mentioned, so the description does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Search the device catalog') and clarifies scope as built-in typical devices plus imported vendor models, which tells an agent what corpus it queries. It does not differentiate from siblings such as device_list or library_import_model, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: the example queries show that fuzzy/keyword lookups like 'S7-1200' or 'mcb 2p' are expected. There is no statement of when to use this versus device_list or the import flow, and no exclusions or prerequisites.

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