Skip to main content
Glama
cadcraft-electrical-mcp

cadcraft-electrical-mcp

sheet_get

Read-onlyIdempotent

Fetch a sheet's complete definition by ID to inspect electrical documentation content for validation, export, or review.

Instructions

Full definition of one sheet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sheet_id": "<sheet_id>"
    },
    "name": "sheet_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheet_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.5/5.0
Behavior2/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 fully covered by structured data. The description adds nothing beyond that – no mention of what a 'full definition' contains, whether lookup fails for unknown ids, or how large the response may be.

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

Conciseness3/5

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

Five words with no filler, which is efficient, but the brevity crosses into under-specification rather than disciplined conciseness – the single sentence does not front-load the operation, its return, or its alternatives.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 enumerated, but the description still omits the verb and any contrast with sheet_preview, leaving an agent unable to confidently choose between them. For a tool sitting in a large sheet_* family, that is a meaningful gap.

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?

There is one required parameter with 0% schema description coverage, so the description carries some burden. It clarifies the scope as 'one sheet', matching the single sheet_id, and the parameter name is self-explanatory, but no format or source for the id is given.

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

Purpose3/5

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

"Full definition of one sheet" implies a retrieve-one-sheet-by-id operation, and the word "Full" faintly contrasts with the sibling sheet_preview. However, there is no verb (get/fetch/return) and no explicit differentiation from preview, so the agent must infer the operation from the tool name.

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?

The description gives no guidance on when to call this versus sheet_preview, sheet_update, or project_info. The only implied signal is that this returns a 'full' definition, but the condition that selects it over a preview is never stated.

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