Skip to main content
Glama

part_links

Finds datasheet, price, stock, and CAD model links for a manufacturer part number across distributors and component libraries. Use these links when a store or CAD project lacks datasheets or files.

Instructions

Search links for a part: datasheet, price and stock (DigiKey, Mouser, Farnell, LCSC, Octopart, Findchips), and symbol, footprint and 3D model (Component Search Engine, SnapMagic, Ultra Librarian). When DigiKey is in the global distributor list and has a key, also the direct links of DigiKey to the CAD models and the datasheets of the MPN. Use them when the store and the CAD project have no datasheet, and for the CAD files. datasheet-lens does not open these pages: open one with a web tool, or give the links to the user (a CAD site needs a free account for the download). A datasheet that you find: add_document with its URL. Gives one line for each link.

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": {
      "mpn": "<mpn>"
    },
    "name": "part_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
mpnYesThe MPN, best the concrete orderable one, for example TPS7A0233PYCHR.

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, the description carries the full burden and does reasonably well: it discloses a conditional branch (DigiKey direct CAD/datasheet links only when DigiKey is in the global distributor list and has a key), states an external constraint (a CAD site needs a free account for download), and clarifies that the tool does not open pages itself. The only gap is rate limits/failure behavior, which is minor here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is a dense block that interleaves capability lists, conditional DigiKey behavior, prohibitions about datasheet-lens, and follow-up instructions. Every sentence carries information, yet the closing "Gives one line for each link" reads as an afterthought and the structure could be split into clearer purpose/usage/next-step segments.

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 shape need not be explained, and the description still notes one line per link. For a single-parameter read tool with no annotations, the description covers what is returned, under which condition, and what the agent should do with the results, leaving little an agent would need to guess.

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?

There is a single required parameter and schema description coverage is 100%; the schema already says to use the concrete orderable MPN with an example. The description adds no further meaning about the mpn argument, so the baseline of 3 applies.

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?

"Search links for a part" is a specific verb+resource, and the description enumerates exactly which link types come back (datasheet, price/stock from DigiKey, Mouser, Farnell, LCSC, Octopart, Findchips; symbol/footprint/3D from Component Search Engine, SnapMagic, Ultra Librarian). This differentiates it from siblings like search_distributors and find_parts, which return part data rather than URLs. It stops short of naming a sibling outright, so a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete trigger: "Use them when the store and the CAD project have no datasheet, and for the CAD files", which implicitly excludes cases where the datasheet already exists. It also routes the agent onward (open with a web tool, feed a found datasheet into add_document). It does not explicitly compare against find_parts or list_documents, so the alternative-selection is only partially covered.

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