Skip to main content
Glama

sheetsdata-mcp

by io.github.octoco-ltd

read_datasheet

Read-only

Read from a component's datasheet. Two modes:

Section mode (default): Returns a named section. Start with section='summary' to get an overview and a list of available_sections. Then request specific sections by name. Section names are dynamic — any heading in the actual datasheet works (e.g. 'register_map', 'i2c_interface', 'power_management'). If a section name isn't found, automatically falls back to search mode.

Search mode: Semantic search within the part's datasheet. Best for targeted questions (register bit fields, I2C config, specific specs). Use when you need to find specific information rather than a whole section.

First call for a new part triggers extraction (30s-2min). Subsequent calls are cached.

Datasheet vs Reference Manual: Manufacturer datasheets cover high-level specs, pinout, absolute maximum ratings, and package info. For microcontrollers (STM32, nRF52, RP2040), register-level programming details (I2C CR1/CR2, DMA config, interrupt bits) are in a separate Reference Manual, not the datasheet. The summary's available_sections will show what's actually present.

The part_number must be a specific manufacturer part number (e.g. 'TPS54302', 'STM32F446RCT6') or LCSC number (e.g. 'C2837938'). Do NOT pass bare component values ('100nF', '10K'), descriptions, or reference designators.

DATASHEET STATUS VALUES:

  • 'ready' — extracted and indexed; call read_datasheet, search_datasheets, or analyze_image.

  • 'extracting' / 'in_progress' / 'queued' / 'pending' — extraction running or scheduled. Poll check_extraction_status every 5-10s until 'ready' or 'failed'. Typical time: 30s-2min.

  • 'not_extracted' — known part but datasheet hasn't been fetched yet. Trigger it via prefetch_datasheets (cheapest) or by calling read_datasheet (auto-triggers on first read).

  • 'no_source' — we couldn't find a public datasheet URL for this MPN. First, retry prefetch_datasheets in 10-30s (the URL resolver re-runs and often finds a source on the second pass). If still 'no_source', the agent can upload the PDF manually via request_datasheet_upload + confirm_datasheet_upload (see those tools). Org-uploaded datasheets are private to the org.

  • 'unsupported' — PDF exists but can't be extracted (scanned image-only, encrypted, or corrupted). Upload a clean text-based PDF via request_datasheet_upload to override.

  • 'failed' / 'error' — extraction errored. The response includes the error reason. Retry via prefetch_datasheets or escalate to support.

  • 'rejected' — input wasn't a real MPN (bare value like '100nF', description, or reference designator). Fix the input and re-call.

  • 'deduplicated' — another part in the family already has this datasheet; same content is returned under the primary MPN.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoReading mode: 'section' (default) returns a named section, 'search' does semantic searchsection
limitNoMax search results for search mode (default 10). Each result includes adjacent context chunks for continuity.
queryNoSearch query — REQUIRED when mode='search', ignored when mode='section'. Example: 'charge voltage register', 'I2C address'.
sectionNoSection name for section mode. Start with 'summary' to discover available sections. Common: summary, pinout, electrical, abs_max, register_map, timing, package. Any heading in the datasheet works (slugified).summary
part_numberYesSpecific manufacturer part number (MPN) or LCSC number. Not a value or description.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Search query for search mode (e.g. 'charge voltage register', 'I2C address')"New value: +"Search query — REQUIRED when mode='search', ignored when mode='section'. Example: 'charge voltage register', 'I2C address'."
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / default
      Previous value: -5New value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Max search results for search mode (default 5)"New value: +"Max search results for search mode (default 10). Each result includes adjacent context chunks for continuity."
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint and non-destructive behavior, the description discloses that first calls trigger extraction (30s-2min), that section names are dynamic and fall back to search, and provides exhaustive status value semantics. It also explains that register-level details are not in the datasheet for MCUs, preventing incorrect expectations.

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 description is long but densely organized with bold section headers (Section mode, Search mode, Datasheet vs Reference Manual, DATASHEET STATUS VALUES). Each segment earns its place, delivering actionable guidance rather than fluff, though the status value enumeration is extensive and could arguably be trimmed or moved to a linked reference.

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?

Given the tool's complexity (5 params, no output schema), the description is remarkably complete: it covers prerequisite extraction, caching, status handling, error escalation, and even context about datasheet vs reference manual. The agent is fully equipped to decide when and how to call this tool without needing external knowledge.

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

Parameters5/5

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

While the input schema covers all five parameters, the description adds critical meaning beyond the schema: part_number must be a specific MPN or LCSC number (not bare values), section mode should start with 'summary', and search mode requires a query. It gives concrete examples and explains how section names are dynamic slugified headings, supplementing the schema's basic type enums.

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?

The description opens with 'Read from a component's datasheet', a specific verb+resource, and then details two modes (section and search). It distinguishes from sibling tools like search_datasheets by focusing on reading within a single part's datasheet, and the part_number requirement clarifies its scope.

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 description explicitly guides usage: section mode default with summary first, search mode for targeted questions, and a detailed 'Datasheet vs Reference Manual' section explaining when to use this tool versus consulting a reference manual. It also maps status values to next actions (prefetch_datasheets, check_extraction_status, request_datasheet_upload), providing unambiguous when-to-use versus alternative tool guidance.

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

All sheetsdata-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.8/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: search_parts finds parts, search_datasheets searches extracted content, read_datasheet reads sections, analyze_image extracts visual data, compare_parts batches comparisons, find_alternative finds substitutes, check_design_fit validates specs, prefetch/check/manage extraction status, and request/confirm handle uploads. The descriptions cross-reference each other to further eliminate ambiguity.

Naming Consistency5/5

All 12 tools follow the verb_noun snake_case pattern consistently (analyze_image, check_design_fit, compare_parts, prefetch_datasheets, request_datasheet_upload, etc.). No mixing of camelCase, verb styles, or vague generic names.

Tool Count5/5

12 tools is ideal for a datasheet-centric server, covering the full workflow from part discovery and datasheet extraction to analysis, validation, comparison, and upload. The count is neither bloated nor thin, and every tool earns its place.

Completeness5/5

The tool surface is comprehensive for the domain: part search, spec-based semantic search, detailed part data, datasheet reading (section/search), image analysis, design-fit checking, part comparison, alternative finding, extraction lifecycle management, and manual datasheet upload (request+confirm). No obvious dead ends or critical missing operations.

Resources