Skip to main content
Glama

list_parts

Read-only

List the parts library with verification status to confirm which custom components are available; built-in kinds like resistor and capacitor are excluded.

Instructions

List the parts library (parts/) with verification status. Built-in kinds (resistor, capacitor, led, pinheader, …) are not here: guide { topic: "writing-circuits" } lists them.

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": "list_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered and the description need only add value, which it does by disclosing that entries carry verification status and that the source is the parts/ library. It stops short of describing ordering, volume, or entry shape, so it is informative but not rich.

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 sentences, front-loaded with what the tool returns before the exclusion clause. Every clause earns its place: one states scope and payload, the other prevents a likely mis-selection.

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?

For a parameterless read-only listing tool with annotations covering the safety profile and no output schema, the definition gives everything needed to select and call it correctly, including the key boundary against built-in kinds. Only minor gaps remain, such as entry ordering or expected volume for a large library.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the description correctly spends no words on it. It avoids inventing filtering language that would imply parameters that do not exist.

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?

Names a specific verb and resource ('List the parts library (parts/)') plus the payload attribute returned ('with verification status'). It also draws the boundary that matters most here: built-in library kinds are excluded, which separates this tool's subject matter from anything guide-related.

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?

Supplies both an implicit when-to-use (fetching the parts library) and an explicit when-not: built-in kinds such as resistor, capacitor, led, pinheader are not listed here. It routes the agent to the alternative with a concrete call, guide { topic: "writing-circuits" }, so the handoff is actionable rather than a vague pointer.

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