Skip to main content
Glama
Sign In
Text2Sch

Text2Sch

by scooorpion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

altium_library_prepare

Prepare a DbLib-based circuit and native script without launching Altium, enabling structured circuit data to be readied for schematic generation.

Instructions

Prepare a DbLib-based circuit and native script without launching 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_library_prepare"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.3/5.0
Behavior2/5

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

"Without launching Altium" is a genuinely useful behavioral trait beyond the annotations, telling the agent no Altium process/COM automation is required. But the description says nothing about what files are written, where they land, whether existing outputs are overwritten, or what the tool returns — significant omissions for a non-readOnly operation, even though destructiveHint=false.

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?

One short, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is under-specification rather than discipline.

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 non-readOnly tool taking an opaque nested object with no output schema, the description should explain the spec's shape and the produced artifacts. Neither is covered, so the agent cannot reliably invoke it even in principle.

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

Parameters1/5

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

The single required parameter "spec" is a bare object with no declared properties, and schema description coverage is 0%. The description does not name a single field, format, or expected structure for the spec, so an agent has no basis for constructing a valid call.

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?

The description names a concrete verb ("Prepare") and two concrete artifacts ("DbLib-based circuit and native script"), which is more informative than the bare name. However, it never distinguishes this from the closely named siblings altium_prepare and altium_library_build, so an agent cannot tell which of the three 'prepare/build' variants produces what.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool. With siblings altium_library_build, altium_library_validate, and altium_prepare all plausibly applicable, the absence of routing guidance is a real gap.

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