Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

terminals_list

Read-onlyIdempotent

Lists terminal strips and their assigned terminals to support electrical terminal-plan review, wiring documentation, and connection checks.

Instructions

Terminal strips with their terminals.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — no note on scope (project-wide vs sheet-level), ordering, or whether strips are returned with their assigned I/O.

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

Conciseness2/5

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

Brevity here reflects under-specification rather than conciseness: a six-word sentence fragment with no verb and no structure. Nothing is wasted, but nothing useful is conveyed either.

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?

With zero parameters and a declared output schema, the description need not explain return values or arguments, which limits the burden. However, it never states the implicit context needed to call it (an open project/document) or the scope of the listing, which is the remaining gap for a list tool in a project-scoped catalogue.

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

Parameters4/5

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

The tool takes zero parameters, so per the rubric the baseline is 4. There is no parameter meaning for the description to compensate for.

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

Purpose2/5

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

The description is a noun fragment, "Terminal strips with their terminals," which essentially restates the tool name without a verb or scope. An agent can infer it returns terminal strips, but it is not clear whether that means all strips in the project, the current sheet, or the open document, nor how it differs from siblings like terminals_add or terminals_remove.

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

Usage Guidelines1/5

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

There is no guidance at all about when to call this versus alternatives. No prerequisites, no mention of required context such as an open project, and no exclusions are stated.

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