Skip to main content
Glama

lib_get_installed_libraries

Lists the libraries installed in an Altium environment and reports installed versus available totals, covering integrated, schematic, PCB, database, and query libraries whether open or not.

Instructions

List the libraries installed in the Altium environment.

The answer to "what libraries does this installation have?", which no other tool gives: lib_search walks only the SchLibs already open in the workspace, and design_snapshot_inventory has to be handed explicit .SchLib paths. This reads the environment's own list, so it covers .IntLib, .SchLib, .PcbLib, database and query libraries whether or not anything is open.

INSTALLED IS NOT AVAILABLE. Installed libraries are the ones switched on for this environment; available ones are every library it knows about. This returns the installed list and reports the available total beside it, so a library that is present but not switched on shows up as a gap between the two numbers rather than as an absence.

Args: with_counts: True (default) also reports how many components each library holds. That opens every library to count them, so pass False for a fast listing; the count then comes back as -1, meaning not asked rather than empty.

Returns: {"libraries": [{"library_path", "file_name", "library_type", "library_type_ordinal", "component_count"}], "installed_count", "available_count", "counts_included"}. library_type is one of integrated / source / datafile / database / none / query / design_items, or unknown; it reads "unknown" with an ordinal of -1 when a library is installed but missing from the available list, which is a real state and not an error.

Input Schema

NameRequiredDescriptionDefault
with_countsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.9/5.0
Behavior5/5

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

No annotations, so the description carries full burden and does it: it warns that with_counts opens every library (a real performance cost), defines the -1 sentinel as 'not asked rather than empty', and clarifies that 'unknown' type with ordinal -1 is a legitimate state, not an error.

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?

Front-loaded with the core answer, then scope, then the installed-vs-available distinction, then args and returns. Slightly long, but nearly every sentence adds decision-relevant information; only the return-dict restatement overlaps the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists so return values needn't be restated, yet the description adds the semantic gloss agents actually need (library_type enum values, unknown fallback). Nothing required to call it correctly is missing.

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

Parameters5/5

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

Schema coverage is 0% with one boolean parameter, and the description fully compensates: default value, what it enables, the cost of enabling it, and the exact sentinel returned when disabled.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (list) and resource (libraries installed in the Altium environment) and explicitly contrasts itself with lib_search (open SchLibs only) and design_snapshot_inventory (needs explicit paths). An agent can route without opening any schema.

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

Usage Guidelines5/5

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

Names the two alternatives and the exact condition that selects this tool ('what libraries does this installation have?'), plus the scope it covers (.IntLib, .SchLib, .PcbLib, database and query libraries regardless of open state).

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