Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

device_list

Read-onlyIdempotent

Lists all devices in an electrical project, optionally filtered by a specific device kind, to help users review and select components for documentation.

Instructions

List project devices (optionally of one kind).

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

Input Schema

NameRequiredDescriptionDefault
kindNo

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 closed-world scope, so the safety profile is fully covered elsewhere. The description's only added context is that results are project-scoped; it says nothing about ordering, paging, or result volume, so it contributes modestly beyond the annotations.

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?

A single short sentence with zero filler, and the resource is stated before the optional qualifier. It is arguably too terse for a tool with a large enum, but nothing in it is wasted.

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 described. However, for a list tool whose results may be large, the description omits whether it targets the currently open project and whether any filtering beyond kind is needed, leaving a few practical gaps.

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 0%, but the single parameter's enum is fully enumerated in $defs with 38 device kinds, so the value space is self-documenting. The description clarifies that 'kind' is an optional narrowing filter, which is real added meaning, though it does not specify behavior for unknown or null kinds.

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 pairs the verb 'List' with a specific resource, 'project devices', and notes the optional narrowing by kind. It is clearly distinct from the mutation siblings device_add, device_remove, and device_update, though it does not name any read-only alternative it could be confused with.

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?

'Optionally of one kind' implies the filtering scenario, so an agent can infer that omitting the argument yields all devices. There is no explicit when-to-use guidance, no statement about which project is being listed, and no routing to sibling tools for other entity types.

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