Skip to main content
Glama
Sign In
Electronics Docs MCP Server

Electronics Docs MCP Server

by flaco-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

read_doc

Download and index a PDF datasheet from a direct URL to enable full-text search and content extraction for electronics component documentation.

Instructions

Download and index a PDF by direct URL (required for TI /lit/ds/symlink/....pdf links and any PDF not found via lookup). Often works better than lookup when you already have the exact PDF link. Pass part when known. Then use query_doc_content or read_doc_page.

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>",
      "docIdOrUrl": "<docIdOrUrl>"
    },
    "name": "read_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorYesVendor ID: TI, ST, ADI.
docIdOrUrlYesPDF URL to download and index.
partNoOptional part number for metadata (strongly recommended; avoids UNKNOWN part rows).
titleNoOptional document title for metadata.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description adds behavioral context: downloads and indexes a PDF, requires direct URL, recommends part to avoid UNKNOWN rows. Hints at side effects (indexing) and prerequisites.

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?

Concise, front-loaded, every sentence adds value. No redundancy.

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

Completeness4/5

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

Covers usage context, parameter emphasis, follow-up actions. Lacks output description, but no output schema is provided. Complete enough for effective agent use.

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%, but description adds value by emphasizing 'part' as strongly recommended and clarifying docIdOrUrl as PDF URL. Enhances understanding beyond schema.

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?

Clearly states the tool downloads and indexes a PDF by direct URL, specifying it's for TI links and PDFs not found via lookup. Distinguishes from sibling tools like 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly describes when to use (direct URL required, better than lookup with exact link) and what to do after (use query_doc_content or read_doc_page). Lacks explicit when-not-to-use, but context is clear.

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