Skip to main content
Glama

library_device

Read-only

Read installed device pins, geometry, hidden supplies, properties, and source library data; use an optional unit A–Z to resolve supported multi-unit packages to physical pin numbers.

Instructions

Read real installed device pins, geometry, hidden supplies, properties and source library. Optional explicit unit A..Z resolves supported homogeneous multi-unit packaging to physical pin numbers.

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": {
      "device": "<device>"
    },
    "name": "library_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNo
deviceYes
library_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description does add real behavioral context: it returns hidden supplies and resolves multi-unit packaging into physical pin numbers only for supported homogeneous cases. It does not say what happens for unsupported or ambiguous units, or what an unknown device/library_path yields.

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 dense sentences with the primary action front-loaded and zero filler. The second sentence is information-rich but slightly compressed, packing the unit format, its optionality, and its applicability conditions into one clause.

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

Completeness4/5

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

With no output schema, the description usefully enumerates what is returned (pins, geometry, hidden supplies, properties, source library), which is the right thing to spell out. Gaps are minor for a read-only three-parameter tool: no error/edge-case behavior and no clarification of library_path versus device resolution.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It explains unit well ('explicit unit A..Z resolves ... to physical pin numbers'), but device and library_path are undocumented beyond their types, leaving two of three parameters to guesswork.

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?

Specific verb 'Read' paired with a concrete resource list: installed device pins, geometry, hidden supplies, properties and source library. 'Real installed' implicitly contrasts with a catalog/search view, but the sibling library_search is never named, so differentiation is left to inference.

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?

No statement of when to use this versus library_search or the native_* read tools, and no prerequisites or failure conditions. The only usage-like content is the note that the unit parameter is optional and works for supported homogeneous multi-unit packaging, which covers one parameter rather than the tool's role.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.