Skip to main content
Glama
Sign In

Octopart

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Octopart Search

octopart_search
Read-onlyIdempotent

Search Octopart for electronic components by manufacturer part number (MPN) or keyword. Returns matching parts with manufacturer, category, median price, total availability, and distributor offers (stock, price breaks, MOQ, lead time). Example: octopart_search({ q: "STM32F407", limit: 5, _apiKey: "client_id:client_secret" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "STM32F407VGT6",
      "limit": 5,
      "_apiKey": "your-octopart-client_id:your-octopart-client_secret"
    },
    "name": "octopart_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesManufacturer part number or keyword, e.g. "STM32F407VGT6", "0.1uF 0603 capacitor"
limitNoMax number of parts to return (default 5, max 20)
_apiKeyYesNexar OAuth2 credentials as "client_id:client_secret". Get a free key ("Welcome 1K" plan) at https://portal.nexar.com
countryNoISO country code for pricing/availability context, e.g. "US" (optional)
currencyNoISO currency code for converted prices, e.g. "USD" (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety and side-effect profile is clear. The description adds useful search and result context, such as available output fields and distributor offers, but it does not discuss rate limits, pagination, exact-match behavior, or error conditions.

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 compact and front-loaded: it states the purpose, the query types, the key output fields, and then provides a small example. There is no filler or redundant restating of the schema.

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?

Together with the schema and annotations, the description gives an agent enough to invoke the tool with q and _apiKey and understand the likely result fields. However, it lacks explicit sibling-tool routing and does not describe result structure or edge cases, which prevents a perfect score.

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 description coverage is 100%, so all five parameters are already documented in the input schema. The description adds a concrete usage example involving q, limit, and _apiKey, but it does not meaningfully expand on the schema's parameter documentation, so the baseline of 3 is appropriate.

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?

The description states a specific action ('Search Octopart'), a clear target ('electronic components'), supported query modes ('MPN or keyword'), and the main output fields. It is not a tautology and is clearly differentiated from a generic name, but it does not explicitly distinguish itself from sibling tools like octopart_part or octopart_multi_match.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives. The description explains what the tool does but does not mention octopart_part, octopart_multi_match, or any conditions for choosing one search variant over another.

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

All Octopart toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources