Skip to main content
Glama
SpectraSynq

mcp-nexar

by SpectraSynq

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NEXAR_CLIENT_IDYesYour Nexar client ID
NEXAR_CLIENT_SECRETYesYour Nexar client secret

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
parts_searchB

Search Nexar/Octopart for parts matching free text.

part_by_mpnA

Search Nexar/Octopart for an exact manufacturer part number.

best_datasheet_urlA

Return the first bestDatasheet URL for a manufacturer part number.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation4/5

Each tool serves a distinct purpose: exact MPN lookup, free-text search, and datasheet URL retrieval. The potential confusion between part_by_mpn and best_datasheet_url is mitigated by clear descriptions of differing outputs.

Naming Consistency2/5

Tool names lack a consistent pattern. 'parts_search' follows a noun-verb structure, while 'part_by_mpn' uses a prepositional phrase and 'best_datasheet_url' is an adjective-noun combination. The inconsistent naming style makes the set feel ad hoc.

Tool Count5/5

With only 3 tools, the server is well-scoped for a focused part-search and datasheet service. Each tool is essential, and the count falls comfortably within the ideal range.

Completeness4/5

The server covers the core functions of part search (exact and free-text) and datasheet retrieval. Minor gaps exist, such as no explicit endpoint for part specifications or availability, but these are likely covered by the part_by_mpn response, making the surface adequate.

Maintenance

ActivityStale
ResponsivenessNo issues