Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

validate

Read-onlyIdempotent

Check electrical projects against a standards profile and consistency rules for designations, I/O, ports, terminals, cross references, and cabinet fit or spare space.

Instructions

Check the project against the standards profile and consistency rules (designations, I/O, ports, terminals, cross references, cabinet fit/spare space ...).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the description is not required to explain that nothing is mutated. It does add value by listing the inspection domains, which tells the agent what will actually be examined. It does not disclose whether the tool requires an open/loaded project, whether it short-circuits on the first violation, or whether the '...' scope includes undocumented checks.

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 front-loaded sentence that leads with the action and the reference standard, then packs the check categories into one parenthetical. No wasted wording. Minor deduction: the trailing ellipsis leaves the check list open-ended and slightly vague about the full scope.

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?

For a zero-argument, read-only action with an output schema (so return values need not be described), the description gives enough scope for an agent to call it correctly. The remaining gap is operational context — whether the project must already be open and how this relates to build/reports workflows — which would make it fully complete.

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 and the schema coverage is reported as 100%, so there is no parameter meaning the description needs to supply. Baseline for a zero-parameter tool applies.

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 target ('Check the project') plus the standard it is checked against ('standards profile and consistency rules'), then enumerates concrete check domains (designations, I/O, ports, terminals, cross references, cabinet fit/spare space). An agent knows exactly what the tool does. It stops short of distinguishing this from sibling tools such as 'reports' or 'build', which could also surface project state.

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: an agent can infer it should call this to verify a project's conformance, but the description gives no explicit trigger ('run before build/reports'), no prerequisites (whether a project must be open), and no statement of when not to use it or which sibling to prefer instead.

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