Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

project_info

Read-onlyIdempotent

Retrieve a summary of the active electrical project, including title-block data, counts, potentials, sheets, and cabinet details, to verify project scope before generating documentation.

Instructions

Summary of the active project: title-block data, counts, potentials, sheets, cabinet.

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

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.7/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 openWorldHint=false, so the safety profile is covered. The description adds the useful scope constraint that it reports on the active project and lists the categories of data included, but it does not disclose behavior when no project is active or any other operational context.

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

Conciseness5/5

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

The definition is a single compact sentence with no wasted wording, and it front-loads the core purpose ('Summary of the active project') before listing the included data categories. Every clause contributes to selection or 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 simple, zero-parameter, read-only summary tool with an output schema, the description is nearly complete: it identifies the scope and the kinds of data returned. The main omission is the implicit prerequisite that an active project must exist, and what happens if none is open.

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 there are no parameter semantics to clarify. The schema is empty and fully described by its structure; the description does not need to compensate for any undocumented inputs.

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 states a clear resource and scope: a summary of the active project, including title-block data, counts, potentials, sheets, and cabinet. This distinguishes it from project_list and project_open by focusing on the currently active project rather than managing or listing projects, though it does not explicitly name any sibling.

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 implied by 'active project' — an agent should call it when it needs an overview of the currently open project. However, there is no explicit guidance on when to prefer this over project_list, project_open, or sheet_get, and no stated prerequisite that a project must already be active.

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