Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_search_partnumberandmanufacturer

Read-only

Search Mouser parts by specific manufacturer and one or more Mouser part numbers, returning up to 50 matching results.

Instructions

[SearchApi] POST /api/v1/search/partnumberandmanufacturer This method is deprecated, please use api/v2/search/partnumberandmanufacturer. Search parts by part number and specific manufacturer. Return a maximum of 50 parts. Please review the SearchByPartMfrRequest item in the Models section below to view the detailed description of request parameters.

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": {
      "request": "<request>"
    },
    "name": "post_search_partnumberandmanufacturer"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real context beyond that: the deprecation status and the 50-part result ceiling. It stops short of describing paging (whether 50 is a hard cap or a page size), authentication needs, or the shape of the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the HTTP method and path, then deprecation, then purpose and cap — the important routing information comes first. It is slightly redundant, repeating the same "search parts by part number and specific manufacturer... maximum of 50 parts" sentence that already appears inside the schema.

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

Completeness3/5

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

For a deprecated, nested-object search endpoint with no output schema, the definition covers purpose, cap, and replacement, which is most of what an agent needs. It leaves the response payload and the paging behavior unexplained and outsources parameter detail to an external Models section, so it is adequate rather than complete.

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?

The nested schema does document each request field (manufacturerId, mouserPartNumber, partSearchOptions, mouserPaysCustomsAndDuties) with examples and format notes, so the underlying parameter meaning is available. However, the description itself only defers — "Please review the SearchByPartMfrRequest item in the Models section below" — pointing to documentation the agent may not have, and adds nothing on its own about the pipe-delimited 10-part-number limit or the enum values.

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 names a specific verb and resource ("Search parts by part number and specific manufacturer") and states the result cap ("maximum of 50 parts"). The deprecation line plus the v2 path effectively points at the successor sibling, though it does not contrast with other near neighbors such as the plain part-number or keyword searches.

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?

It gives an explicit negative signal — "This method is deprecated, please use api/v2/search/partnumberandmanufacturer" — which routes the agent away from this tool. What it lacks is positive selection guidance: no statement of when this v1 call is still appropriate versus post_search_partnumber or post_search_keywordandmanufacturer.

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