Skip to main content
Glama

import_part

Imports a single electronic part by LCSC number from the JLCEDA/EasyEDA library into parts// with its symbol, footprint, and attributes; verify it and use only for personal, non-commercial work.

Instructions

Import one part by its LCSC number when the human asks: symbol, footprint and attributes from the JLCEDA/EasyEDA library into parts//. It is NOT verified: tell the human to check verification.md, and that the import is for personal, non-commercial use only (EasyEDA's terms). Never import in bulk. Needs the internet. Letter-numbered pins (BGA, many USB-C) and bottom pads are refused: use create_part.

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": {
      "lcsc": "<lcsc>"
    },
    "name": "import_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoDefault from the MPN
lcscYese.g. C7950
replaceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The description carries real behavioral context beyond the annotations: the result is unverified, the human must be pointed at verification.md, the license is non-commercial only, internet is required, and no bulk imports. What it omits is the overwrite semantics of the `replace` parameter and what happens when parts/<id>/ already exists — material for a tool that writes symbol/footprint files.

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?

The core action and location are front-loaded, and the caveats follow in a logical order (unverified → licensing → limits → prerequisites → refusals). It is dense and slightly run-on, packing several obligations into single sentences, but no sentence is filler.

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 three-parameter import tool with no output schema, the description covers outcomes, licensing, network requirement, and refusal cases, which is what an agent needs before invoking. The remaining gap is the unspecified `replace` behavior on pre-existing part directories.

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 67% and the description clarifies `lcsc` as the identifying key and implies `id` from the parts/<id>/ output path. The `replace` boolean has no description in either the schema or the prose, so a meaningful parameter stays ambiguous; the description adds only marginal meaning over the schema.

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?

"Import one part by its LCSC number" names a specific verb, resource, and retrieval key, then enumerates exactly what is fetched (symbol, footprint, attributes) and where it lands (parts/<id>/). It also pre-empts confusion with create_part by naming the part shapes this tool refuses.

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?

The trigger is explicit ("when the human asks"), bulk use is explicitly forbidden, and the excluded cases (letter-numbered pins, bottom pads) are routed to a named alternative, create_part. An agent has no inference left to do about when to call this versus create_part.

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