Skip to main content
Glama

list_parts

Lists stored electronic parts with manufacturer and document counts, including base-part documents, to show which components have datasheets available.

Instructions

The parts in the store, with their manufacturer and the number of their documents. Gives one line for each part: "MPN (manufacturer): N documents". A concrete part also gets the documents of its base part: "0 own documents, 1 of the base part AP63203". list_documents gives the documents of a part.

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations to lean on, the description still discloses a non-obvious behavior: a concrete part inherits documents from its base part, illustrated as '0 own documents, 1 of the base part AP63203'. That aggregation quirk is exactly the kind of detail an agent could not infer, though read-only status and result ordering go unstated.

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?

Content is front-loaded with what is listed, followed by the exact output format and the base-part edge case. The inline quoted examples are compact and earn their space, though the phrasing 'Gives one line for each part' is slightly redundant with the surrounding text.

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?

An output schema exists, so return values need not be explained, yet the description still supplies the line format and the base-part aggregation rule, which is more than required. The only soft gap is that ordering or scoping of the store (e.g. which parts are included) is left to the schema.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline applies. The description's effort is spent on output shape instead, which is appropriate here.

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 states a specific resource and scope: 'The parts in the store, with their manufacturer and the number of their documents.' It also distinguishes itself from the sibling list_documents, which makes the tool separable from its nearest alternative without reading a schema.

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?

It names list_documents as the tool for a part's documents, which implicitly routes the agent away from this tool for that need. There is no explicit when-to-use statement or precondition, so the guidance is implied rather than stated.

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