Skip to main content
Glama
Sign In
Text2Sch

Text2Sch

by scooorpion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

altium_build

Creates a new isolated Altium project, saves, reopens, compiles it, and compares actual pin networks to verify schematic generation from structured circuit data.

Instructions

Create a NEW isolated Altium project, save/reopen/compile it and compare actual pin networks. Requires licensed local Altium. No UI automation. Not a hardware-design/ERC signoff.

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_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, but the description adds real value beyond them: it needs a licensed local Altium install, it works headlessly, and it creates a NEW isolated project rather than touching existing ones. Missing are failure behavior, runtime expectations for compile, and what the pin-network comparison returns.

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?

Four short, front-loaded statements with the core action first and constraints after; nothing is padded. The telegraphic fragments ("No UI automation.") read a bit like notes, but each clause earns its place.

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?

For a multi-stage build/compile/compare tool with no output schema, the description covers the workflow steps, prerequisites, and scope boundaries adequately. The critical gap is the completely undocumented nested `spec` object, which the agent must supply to call the tool at all.

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?

There is a single required `spec` parameter that is a free-form nested object with 0% schema description coverage, and the description says nothing about its shape, required fields, or format. With a nested opaque object the schema cannot compensate, so the agent has no way to construct a valid call from this definition.

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 and resource ("Create a NEW isolated Altium project") and enumerates the pipeline it runs: save, reopen, compile, and compare actual pin networks. "Not a hardware-design/ERC signoff" separates it from altium_validate, though it never explicitly contrasts with altium_prepare or altium_library_build.

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

Usage Guidelines4/5

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

Gives a hard prerequisite ("Requires licensed local Altium") and two exclusions ("No UI automation", "Not a hardware-design/ERC signoff") that rule out the wrong expectations. It stops short of naming a sibling to use instead when the agent actually wants ERC or library work.

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