Skip to main content
Glama

Search the component library

datasheetvend_search_component_library
Read-onlyIdempotent

Search DatasheetVend's component library: parts from dozens of manufacturers whose manufacturer datasheet DatasheetVend stores. Search by part number, vendor, package, architecture or application words (for example 'STM32 QFN', 'ESP32', 'BLE wearable', 'Cortex-M4'), optionally filtered by vendor, package family, category, pin range or Verified Pack. Each result gives the part page, the stored datasheet PDF (often a family datasheet covering several ordering codes), the manufacturer's own URL when known, whether a curated Verified Pack exists, and the address of the part-pack manifest (a lookup that may answer 'no shelved pack'). A result is a stored datasheet, not extracted data: to extract it, pass its datasheet_pdf_url to an extraction tool. Any one search word can match a row; results are ranked, paged with offset, and do not report a total. Free, no API key, no model call.

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": {
      "query": "<query>"
    },
    "name": "datasheetvend_search_component_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page, default 10.
queryYesSearch words: part number, vendor, package, architecture or application, separated by spaces.
offsetNoSkip this many results (from next_offset).
vendorNoVendor slug such as 'stmicroelectronics' or 'espressif', or part of the vendor's name.
categoryNoPart category as the library page files it.
pin_rangeNolow: up to 16 pins; mid: 17-64; high: 65-144; extreme: 145 or more.
package_familyNoPackage family as the library page groups them.
verified_pack_onlyNoOnly parts that have a curated Verified Pack.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: no API key or model call, results ranked and paged by offset with no total reported, and any single search word can match a row. It also discloses the return shape (part page, stored PDF possibly family-wide, manufacturer URL, Verified Pack flag, manifest address that may report 'no shelved pack').

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?

Purpose is front-loaded in the opening clause and the paragraph follows a logical order: what to search, how to filter, what comes back, what it is not, then paging and cost. It is dense and run-on, with nested parentheticals ('a lookup that may answer \'no shelved pack\'') that could be trimmed, but nearly every clause carries information.

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?

With no output schema and eight parameters, the description still explains the result fields, paging behavior, absence of a total count, and the extraction handoff. Combined with full schema coverage, an agent has everything needed to call it and interpret results 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 coverage is 100%, including per-parameter descriptions and enum explanations for pin_range, package_family and category, so the schema does most of the work and the baseline is 3. The description adds real meaning with the OR-matching rule ('any one search word can match a row') and query examples, but adds nothing about limit/offset/vendor beyond what the schema already documents.

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?

States a specific verb and resource ('Search DatasheetVend's component library') and enumerates the searchable facets (part number, vendor, package, architecture, application). It explicitly separates itself from the extraction tools by saying a result is a stored datasheet, not extracted data. It does not distinguish itself from the sibling datasheetvend_search_document, which is the one remaining ambiguity.

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?

Gives concrete query examples ('STM32 QFN', 'ESP32', 'BLE wearable', 'Cortex-M4') and a clear next-step rule: pass datasheet_pdf_url to an extraction tool if you need extracted values. It does not say when to prefer this over datasheetvend_search_document, so the search-vs-search choice is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources