Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

symbols_list

Read-onlyIdempotent

List available electrical symbols by style for current-path elements and retrieve each symbol ID to use in PathElement.symbol.

Instructions

Symbols available for current-path elements (use the id in PathElement.symbol).

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": "symbols_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoiec

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered elsewhere. The description adds the meaningful scoping detail that results depend on the 'current path', but does not explain what 'current path' means or how it is set.

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?

One short sentence with the resource and its usage packed front-first, no filler. The phrasing is slightly telegraphic ('current-path elements'), which costs a point on clarity but nothing on economy.

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?

An output schema exists, so return values need not be explained. However, for a tool whose results depend on 'current path' and which exposes an unexplained 'style' variant, the description leaves real ambiguities about context requirements and style options.

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?

There is a single optional parameter 'style' (default 'iec') with 0% schema description coverage, and the description never mentions it, so no meaning is added for the one input that exists. With only one parameter and a default value, the gap is limited, keeping this near the baseline rather than below it.

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?

States the resource returned (symbols) and its scope (available for current-path elements), plus the intended use of the result id in PathElement.symbol. The verb 'list' is only implied, but an agent can tell this is a read of the symbol catalog rather than a project/device listing.

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?

The parenthetical 'use the id in PathElement.symbol' gives an implicit when-to-use cue: call this to resolve a symbol id for path elements. There is no explicit statement of alternatives or of preconditions such as needing a project or path open, so guidance is implied rather than stated.

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