Skip to main content
Glama
Sign In
Electronics Docs MCP Server

Electronics Docs MCP Server

by flaco-source
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_indexed_documents

Retrieve indexed PDF documents for a vendor, optionally filtered by part number, returning count and document metadata.

Instructions

List indexed PDF metadata from the local database (no web fetch). Returns count and documents (id, part, title, docType, url, indexedAt). Optional part filters to that part number (normalized like other tools). Omit part to list all documents for the vendor.

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

Input Schema

NameRequiredDescriptionDefault
vendorYesVendor ID: TI, ST, ADI.
partNoOptional part number (e.g. **STM32G071RB**). If omitted, all indexed docs for the vendor are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, so description bears full burden. It discloses that the tool performs a local database read (no web fetch) and returns specific fields. For a read-only listing tool, this adequately covers behavioral traits.

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?

The description is concise (three sentences), front-loaded with the most important information, and every sentence serves a purpose without redundancy.

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?

Despite no output schema, the description fully explains the return structure (count and documents with specific fields). It covers optional filtering and key traits, making it complete for this simple tool.

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 explaining 'part' is normalized like other tools and omitting it lists all documents for the vendor. This provides context beyond the raw 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?

The description explicitly states the tool lists indexed PDF metadata from the local database (no web fetch), distinguishes from siblings by emphasizing local-only operation, and clearly specifies return fields (count, documents with id, part, title, docType, url, indexedAt).

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?

The description provides clear context on when to use (listing indexed docs locally) and guidance on the optional 'part' filter. It lacks explicit when-not-to-use or alternative tools, but the context is sufficient for basic decisions.

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