Skip to main content
Glama
Sign In
Text2Sch

Text2Sch

by scooorpion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

altium_validate

Read-only

Validate a single-sheet, flat, or hierarchical circuit specification without opening Altium to catch errors before generating schematics.

Instructions

Validate a single-sheet, flat or hierarchical circuit specification without opening Altium.

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": {
      "spec": "<spec>"
    },
    "name": "altium_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful context that Altium need not be opened or installed, but it does not explain what validation checks run, what happens on failure, or what the result reports.

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?

It is a single, front-loaded sentence that names the action and scope without redundant restatement. Nothing in the sentence is wasted.

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?

There is no output schema, so the description should at least indicate what validation returns, such as pass/fail or a violation list, but it does not. The nested spec parameter also lacks structural guidance, making the definition incomplete for an agent to invoke it confidently.

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

Parameters2/5

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

The sole parameter 'spec' is an untyped nested object with 0% schema description coverage. The description only calls it a 'circuit specification' and gives no expected fields, nesting, or format, leaving the most important input underdefined.

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?

States a specific verb ('Validate') and resource ('circuit specification'), plus accepted topologies: single-sheet, flat, or hierarchical. It does not distinguish this tool from the sibling altium_library_validate or clarify what kinds of validation are performed.

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 explicit when-to-use or when-not-to-use guidance, and no alternative siblings are named. The phrase 'without opening Altium' implies a pre-build validation step, but the agent must infer how this differs from altium_prepare, altium_doctor, or altium_library_validate.

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

Deploy Server

Other Tools