Skip to main content
Glama

download_registry_part

Download a parts-registry part's files, such as footprint, symbol, STEP, or preview, into an existing local folder for use in KiCad projects.

Instructions

Download the files of a part of the parts registry into a local folder.

The tool downloads only through HTTPS, only from the hosts of the registry, at most 50 MB for each file, and only the file extensions of each format.

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": {
      "part_id": "<part_id>",
      "save_dir": "<save_dir>"
    },
    "name": "download_registry_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatsNoThe files to download: "footprint", "symbol", "step" and "preview". Default: the footprint and the symbol.
part_idYesThe ID of the part (search_parts_registry gives it).
save_dirYesA folder that exists, for example the library folder of the project: in the working folder, the home folder or a folder of PARTS_REGISTRY_SAVE_ROOTS.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does so well for the security and limits profile: HTTPS-only transport, registry hosts only, a 50 MB per-file cap, and restriction to each format's permitted file extensions. What is missing is mutation behavior on the destination, such as whether existing files are overwritten or what happens when a file exceeds the size cap.

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 sentences, front-loaded with the action and followed by the constraint set; nothing is wasted. The phrasing 'a part of the parts registry' is slightly clumsy but not costly.

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 no explanation, and the description covers the transport, host, size, and format-extension constraints that govern a successful call. Remaining gaps, overwrite semantics and error behavior, are modest for a straightforward download tool.

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 coverage is 100%, so all three parameters (formats, part_id, save_dir) are already documented with defaults and examples. The description only echoes the formats constraint ('only the file extensions of each format') without adding syntax or selection guidance beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb and resource: 'Download the files of a part of the parts registry into a local folder.' That is unambiguous and clearly distinct from metadata-style siblings like get_registry_part or search_parts_registry. It stops short of naming those siblings, so the differentiation is implicit rather than explicit.

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?

There is no when-to-use / when-not-to-use guidance and no alternatives are named. The only routing hint, that a part ID comes from search_parts_registry, lives in the schema's part_id description, not in the tool description. An agent must infer that this is the follow-up step after finding a part.

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