Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

standards_info

Read-onlyIdempotent

Get standards profile details and validation rules for device codes, wire colors, sheet formats, text heights, and terminal marking to ensure compliant electrical documentation.

Instructions

Rules of a standards profile: letter codes per device kind, wire colours, sheet format, text heights, terminal marking, available profiles and validation rules.

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

Input Schema

NameRequiredDescriptionDefault
profileNo

Output Schema

NameRequiredDescriptionDefault

No arguments

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=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is fully covered by structured data. The description adds that the response is a body of rules covering multiple standards aspects, including the list of available profiles, which is genuinely useful behavioral context. It does not disclose default behavior when profile is omitted, which limits it to a 3.

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 sentence with a compact, comma-separated enumeration of contents — front-loaded on the resource and free of filler. The colon-list format is scannable, though the enumeration is a little dense with no sentence explaining the key profile-selection behavior.

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, and the annotations cover the safety profile. The remaining gap is the one optional parameter: for a tool whose whole purpose is profile-scoped rule lookup, the description never says how profile selection works or what the no-argument case yields.

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?

Not applicable placeholder correction: schema description coverage is 0% for a single optional 'profile' parameter with default null, so the description must carry the burden. It mentions 'available profiles' and 'rules of a standards profile', which at least implies the parameter selects among profiles, but it never states how the argument is formatted or what is returned when it is null/omitted. Two points of meaning are implied but not confirmed, so it falls short of a full pass despite the hint.

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 the resource specifically (a standards profile) and enumerates its contents — letter codes, wire colours, sheet format, text heights, terminal marking, profiles, validation rules — so an agent knows this is a standards/rules lookup rather than a project query. It does not explicitly say 'returns' or distinguish itself from project_info, but the content enumeration is concrete enough to identify the tool.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus siblings such as project_info or the cabinet/device tools, and no statement about prerequisites. The most important usage question — whether to call it with no profile argument to discover profiles, or with one to fetch a specific profile's rules — is never addressed.

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