Skip to main content
Glama
Sign In

SheetsData

by io.github.octoco-ltd
OverviewDiscussionsAdmin

Get Part Details

get_part_details
Read-only

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. Known lifecycle risks carry lifecycle_warning. Discovered in-document errata_sections and application_circuit_sections include names for read_datasheet (use read_args when supplied); absence does not prove the manufacturer has no separate errata. 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.

Input Schema

NameRequiredDescriptionDefault
compactNoReturn the shorter answer: prose written for another part comes back as family_summary instead of a labelled datasheet_summary. Default false: the full answer.
verboseNoReturn every available_sections entry. By default the first 50 are returned, plus a '_truncated' entry saying how many more exist.
providerNoWhich provider's sources to show (default 'all').all
part_numberYesSpecific manufacturer part number (MPN) or LCSC number (e.g. 'TPS54302DDCR', 'C2837938'). Not a value ('100nF'), description or reference designator ('R1').
prefetch_datasheetNoStart background datasheet extraction (no extra charge).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the readOnly/openWorld annotations: it discloses cost behavior ('Free', prefetch at no extra charge), that resolved_as/data_quality_warning flag MPN mismatches, that lifecycle_warning marks risks, and cautions that absence of errata_sections does not prove absence of manufacturer errata. This is unusually rich behavioral context, though it leaves the return shape itself partly implicit.

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 routing guidance is front-loaded and valuable, but the body is a dense run-on paragraph with nested parentheticals (e.g. the read_datasheet / read_args aside) that is hard to scan. Much earns its place, but the structure could be broken into clearer segments.

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?

For a 5-parameter read tool with no output schema and heavy cross-tool interplay, the description covers purpose, cost, edge cases, warning fields, and downstream routing comprehensively. An agent has everything needed to call it and interpret the result correctly.

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 description coverage is 100%, so the schema already documents all five parameters including compact, verbose, provider and prefetch_datasheet. The description mostly restates these (e.g. family_summary for compact, 'no extra charge' for prefetch), adding little interpretation beyond what the schema provides.

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 and resource and enumerates exactly what the response contains (provider specs, price, stock, lifecycle, specialized_specs, datasheet_summary, datasheet_status, errata_sections). It is clearly distinguishable from siblings like search_parts, read_datasheet and check_extraction_status.

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', and provides a complete decision table mapping datasheet_status values ('ready', 'extracting', 'not_extracted', 'no_source') to the specific sibling tool to call next. When-to-use and alternatives are fully specified.

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

All SheetsData toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources