digikey-list-mcp

digikey_get_part

Read-only

Retrieve current DigiKey product details, variations, stock, lifecycle status, and pricing for a specified part number to validate components and support purchasing decisions.

Instructions

Get current exact product, variation, stock, lifecycle, and pricing data from DigiKey.

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": {
      "product_number": "<product_number>"
    },
    "name": "digikey_get_part"
  }
}

Input Schema

Name	Required	Description	Default
`product_number`	Yes
`manufacturer_id`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful context that data is 'current' and 'exact,' suggesting live external lookups. However, it does not mention rate limits, authentication requirements, or what happens when a part number is not found.

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?

A single, well-structured sentence that front-loads the core purpose and lists the data categories retrieved. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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. However, with zero schema description coverage on two parameters, the description is incomplete for an agent to call this tool correctly without guessing parameter formats and the role of manufacturer_id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning neither parameter is documented in the schema. The description adds no information about what product_number or manufacturer_id should contain, how to format them, or when manufacturer_id is needed. With two parameters and zero schema coverage, the description should compensate but does not.

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?

States a specific verb (Get) and resource (product/part data) with the exact data categories retrieved: product, variation, stock, lifecycle, and pricing. An agent can distinguish this from digikey_search_parts because the description emphasizes retrieving 'current exact' data for a known part rather than searching.

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?

The word 'exact' implies this is for retrieving a specific known part rather than searching, which differentiates it slightly from digikey_search_parts. However, there is no explicit statement of when to use this versus digging through search results, and no mention of prerequisites or error conditions.

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

Deploy Server