Skip to main content
Glama
Sign In
Text2Sch

Text2Sch

by scooorpion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

altium_prepare

Generates isolated Altium script files and an SVG preview from a structured circuit specification, so agents can prepare schematic output without executing Altium.

Instructions

Write isolated script files and a specification SVG preview. Does not execute 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_prepare"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that the tool mutates state by writing files and that it deliberately stops short of executing Altium, but it omits where files are written, whether existing files are overwritten, and any permission or sandbox constraints.

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?

Two short sentences, front-loaded with the productive action and followed by the safety-relevant exclusion. No filler, though the brevity borders on under-specification rather than tightness.

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?

For a tool taking an opaque nested object with no output schema and no annotations, the description is far too thin: an agent cannot construct a valid `spec` or predict what files will appear. The only complete information conveyed is the non-execution guarantee.

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?

Schema description coverage is 0% and the sole parameter is an unconstrained nested object, so the agent receives no field-level guidance from either schema or description. The phrase "specification SVG preview" hints that `spec` describes a design specification, but its required keys and their formats are never stated.

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?

"Write isolated script files and a specification SVG preview" names concrete artifacts (script files, SVG preview), so the verb+output are identifiable. However, the description never says what is being prepared or for which Altium workflow, and the negative clause "Does not execute Altium" only partially separates it from altium_build/altium_library_prepare.

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?

The single exclusion "Does not execute Altium" implies altium_build is the tool that runs the prepared output, which is useful routing context. There is no explicit statement of when to call this versus altium_build or altium_library_prepare, and no prerequisites (e.g., needed inputs before preparing).

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