Skip to main content
Glama
Sign In
Text2Sch

Text2Sch

by scooorpion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

altium_doctor

Read-only

Runs read-only diagnostics for the Altium executable, running processes, and desktop locks to identify environment issues before schematic generation.

Instructions

Read-only executable, process and desktop-lock diagnostics. Does not prove the scripting engine is responsive.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "altium_doctor"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

The readOnlyHint annotation already marks it as non-mutating; the description adds the diagnostic scope and an important boundary: it does not prove the scripting engine is responsive. It still omits whether a running Altium instance is required and what kinds of checks are performed.

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?

Two compact sentences, with the read-only diagnostic scope front-loaded and the limitation following. No filler is present, though the noun-list style is slightly compressed.

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 no-parameter diagnostic tool with a readOnly annotation and no output schema, the definition covers the core scope and a key limitation. It remains thin on invocation context—prerequisites and expected output—which an agent may need in order to choose it confidently.

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

Parameters4/5

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

With zero input parameters, there are no parameter semantics to document, so the zero-parameter baseline applies. The description correctly avoids inventing parameter behavior.

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?

The description names concrete diagnostic domains—executable, process, and desktop-lock—and labels the operation read-only, distinguishing it from the library/build siblings. It is specific but telegraphic, never using a full verb phrase such as 'diagnose'.

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 guidance on when to run this versus altium_validate or the other siblings, nor any stated prerequisites such as whether Altium must be running. The only usage-like guidance is the limitation that it does not prove scripting engine responsiveness.

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