SheetsData MCP

Get Part Details

get_part_details

Read-only

Get full specs, pricing, stock, lifecycle, and datasheet status for a single electronic component by MPN or LCSC number. Use after search_parts to drill into one result.

Instructions

Free. Full details for one part: provider specs, price, stock and lifecycle, the per-MPN structured values (specialized_specs), the cached datasheet summary, and datasheet_status with available_sections when ready. If any of it is for a different MPN than you asked for (an orderable variant, a base part, a sibling's datasheet), resolved_as and data_quality_warning at the top of the response say so, and prose written for another part is labelled as such at the start of datasheet_summary (family_summary with compact=true): trust specialized_specs for numbers. prefetch_datasheet=true starts extraction at no extra charge. Use after search_parts to drill into one result. datasheet_status: 'ready' → read it; 'extracting' / 'queued' / 'pending' / 'resolving' → poll check_extraction_status; 'not_extracted' → prefetch_datasheets; 'no_source' / 'unsupported' → request_datasheet_upload. Full list in the server instructions.

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_number": "<part_number>"
    },
    "name": "get_part_details"
  }
}

Input Schema

Name	Required	Description	Default
`compact`	No	Return the shorter answer: prose written for another part comes back as family_summary instead of a labelled datasheet_summary. Default false: the full answer.
`verbose`	No	Return every available_sections entry. By default the first 50 are returned, plus a '_truncated' entry saying how many more exist.
`provider`	No	Which provider's sources to show (default 'all').	all
`part_number`	Yes	Specific manufacturer part number (MPN) or LCSC number (e.g. 'TPS54302DDCR', 'C2837938'). Not a value ('100nF'), description or reference designator ('R1').
`prefetch_datasheet`	No	Start background datasheet extraction (no extra charge).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.4.0Oct 17, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "Return the shorter answer: prose written for another part comes back as family_summary instead of a labelled datasheet_summary. Default false: the full answer.",
+  "type": "boolean"
+}

changedInput schema / properties / part_number / description

Previous value: -"Specific manufacturer part number (MPN) or LCSC number (e.g. 'C2837938'). Not a value or description."New value: +"Specific manufacturer part number (MPN) or LCSC number (e.g. 'TPS54302DDCR', 'C2837938'). Not a value ('100nF'), description or reference designator ('R1')."

changedInput schema / properties / prefetch_datasheet / description

Previous value: -"Trigger background datasheet extraction (no extra charge). Default false."New value: +"Start background datasheet extraction (no extra charge)."

changedInput schema / properties / provider / description

Previous value: -"Which provider to query: 'all' (default), 'jlcpcb', 'mouser', or 'digikey'"New value: +"Which provider's sources to show (default 'all')."

addedInput schema / properties / verbose

Added value: +{
+  "default": false,
+  "description": "Return every available_sections entry. By default the first 50 are returned, plus a '_truncated' entry saying how many more exist.",
+  "type": "boolean"
+}

First observedv1.0.0Mar 22, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/destructive/openWorld and cost, so the bar is lower, yet the description adds substantial context: cost ('Free', and prefetch 'at no extra charge'), MPN-mismatch disclosure via resolved_as/data_quality_warning, labelling of foreign prose in datasheet_summary, and a trust rule ('trust specialized_specs for numbers'). That is real behavior beyond structured fields.

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?

Front-loads the highest-value facts ('Free. Full details for one part: ...') and every sentence carries information, including the status routing rules. It is a dense single paragraph with some repetition ('Free' vs 'no extra charge') and is long enough that a reader must scan carefully, which is a minor structural cost.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the full burden of describing returns, and it does so by naming the key response fields (specialized_specs, datasheet_summary, datasheet_status, resolved_as, data_quality_warning). Combined with the status routing and the pointer to server instructions, an agent has everything needed to call and interpret this tool correctly.

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?

Schema coverage is 100%, so the schema already documents all five parameters and baseline is 3. The description nonetheless adds meaning: the effect of compact (family_summary vs labelled datasheet_summary), the no-extra-charge property of prefetch_datasheet, and the 'trust specialized_specs for numbers' guidance tied to compact. The provider enum and verbose are not elaborated in prose, keeping it short of a 5.

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+resource ('Full details for one part') and enumerates exactly what comes back: provider specs, price, stock/lifecycle, specialized_specs, datasheet summary, datasheet_status with available_sections. It also distinguishes itself from search_parts by positioning itself as the drill-down step, so an agent can tell it apart from sibling search tools.

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?

Explicitly says 'Use after search_parts to drill into one result', then provides a status-to-alternative routing table ('extracting' → check_extraction_status, 'not_extracted' → prefetch_datasheets, 'no_source' → request_datasheet_upload). This is textbook when-to-use/when-to-use-something-else guidance naming the exact sibling tools.

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

Deploy Server