Skip to main content
Glama

part_info

Read-only

Retrieves a library part's part.yaml, footprint pad details, and verification checklist to inspect component data before PCB design.

Instructions

Show a library part's part.yaml, its footprint's pads and the verification checklist.

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": {
      "id": "<id>"
    },
    "name": "part_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint=true / destructiveHint=false annotations already establish the safety profile, so the description only needs to add context. It does add value by naming the three returned artifacts, but says nothing about behavior on a missing or ambiguous id, output size, or whether the checklist is computed at call time.

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?

A single front-loaded sentence with no filler; the returned contents are listed compactly. Nothing in it is redundant with the schema or annotations.

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?

With no output schema and a bare single-property input schema, the description is the only place semantics can live, and it covers returns but not the id parameter or error behavior. Adequate to identify the tool, not sufficient to guarantee a correct first invocation.

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?

There is one required parameter, id, with 0% schema description coverage, and the description says nothing about it. It does not clarify whether the id is a library name, a path, or an opaque identifier, which is exactly the ambiguity that would cause a failed call.

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 uses a specific verb ("Show") plus a concrete resource: a library part's part.yaml, its footprint's pads, and the verification checklist. That makes the payload unambiguous, though it never contrasts itself with a lookup sibling such as module_info, so the agent must infer when a part lookup is preferred.

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?

Usage is only implied: an agent can infer this is the inspection call for an existing part, as opposed to create_part, import_part, or set_part_fields. There is no explicit when-to-use, no prerequisites, and no statement about what to call when the part is not in the library.

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