Skip to main content
Glama
Sign In
Electronics Docs MCP Server

Electronics Docs MCP Server

by flaco-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_docs

Retrieve PDF links (datasheets, technical reference manuals, application notes) for electronic components from TI, ST, and ADI by providing a vendor ID and part number or search term.

Instructions

Primitive: list PDF links (datasheet, TRM, app notes) for a part from the vendor site. Does not index. After lookup returns only suggestions, you can use this for a fuller link list.

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

Input Schema

NameRequiredDescriptionDefault
vendorYesVendor ID: TI, ST, ADI.
queryYesPart number or search term (e.g., 'LM317', 'BQ40Z50', 'BQ40Z50-R5', 'ADAU1701').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Discloses it does not index and relationship to lookup results. No annotations exist, so description carries full burden. Lacks details on read-only nature, rate limits, or authentication.

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?

Two sentences, front-loaded with key action. No unnecessary words. Efficient and well-structured.

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?

Adequate for low complexity tool with full schema. Explains purpose and behavior relative to lookup. Lacks output format details, though implied by 'list PDF links'. No output schema to compensate.

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 already fully describes parameters (vendor, query). Description adds little beyond mentioning 'vendor site', which aligns with vendor parameter. Baseline score applies.

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?

Clearly states it lists PDF links for a part from vendor site. Distinguishes itself from indexing. However, could more explicitly differentiate from sibling tools like list_indexed_documents and lookup_doc.

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?

Provides context for use after lookup that returns suggestions. But does not explicitly state when not to use or compare to alternatives like lookup_doc or query_doc_content.

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

Deploy Server

Other Tools