Skip to main content
Glama
Sign In

Octopart

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Octopart Part

octopart_part
Read-onlyIdempotent

Get full detail for a single electronic part by exact MPN: every distributor seller with offers (price breaks, inventory level, MOQ, factory lead time), technical specs, availability, datasheet URL, and Octopart page. Example: octopart_part({ mpn: "LM317T", _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": {
      "mpn": "LM317T",
      "_apiKey": "your-octopart-client_id:your-octopart-client_secret"
    },
    "name": "octopart_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
mpnYesExact manufacturer part number, e.g. "LM317T", "ATMEGA328P-PU"
_apiKeyYesNexar OAuth2 credentials as "client_id:client_secret". Get one 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

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds the exact-match constraint and previews the response contents, but it does not disclose auth requirements beyond the schema, rate limits, or not-found behavior. This is acceptable but not rich.

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 a single front-loaded sentence that states the purpose and enumerates the key deliverables, followed by a compact, illustrative example. There is no filler or redundant restatement 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?

For a read-only, single-part lookup with a fully documented schema, the description plus annotations cover the essential information an agent needs. There is no output schema, but the description enumerates the main return fields. Minor gaps like error handling or empty-result behavior are not critical for this tool.

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 the schema already documents all four parameters. The description reinforces 'exact MPN' and provides a concrete example call, but it does not add meaningful semantics for country or currency beyond what the schema already states. Baseline 3 is appropriate.

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 states a specific verb ('Get full detail'), a specific resource ('a single electronic part'), and a precise lookup key ('exact MPN'). It also enumerates the returned content, which makes the tool's scope unmistakable and differentiates it from the octopart_search and octopart_multi_match siblings.

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 phrase 'by exact MPN' and 'single electronic part' clearly implies when to use this tool: when the agent already has an exact manufacturer part number. It does not explicitly name alternatives or say 'use octopart_search for fuzzy matches,' but the sibling names and the 'exact' qualifier provide enough contextual guidance.

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