Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_search_partnumber

Read-only

Search Mouser Electronics parts by one or more part numbers, returning up to 50 matching parts so you can verify exact components and availability.

Instructions

[SearchApi] POST /api/v{version}/search/partnumber Search parts by part number and return a maximum of 50 parts. Please review the SearchByPartRequest 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_partnumber"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes
versionNoAPI version. Defaults to 1.1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 by structured data. The description usefully adds the hard 50-result cap, which affects result-completeness expectations, but says nothing about authentication, throttling, or truncation behavior when more matches exist.

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

Conciseness3/5

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

The core sentence is tight and front-loaded, but the trailing pointer to a 'Models section' that is not included in the definition is dead weight that consumes attention without delivering information. The raw route prefix also adds little for an agent choosing a tool.

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 read-only search tool with no output schema, the definition covers the essential what and the result cap, and annotations carry the safety profile. However, the nested request wrapper, the version parameter's practical effect, and the deferred parameter documentation leave meaningful gaps relative to the schema's 50% coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, so the description is expected to compensate, yet it adds nothing beyond the schema and instead defers to a 'SearchByPartRequest item in the Models section below' that is not part of this definition. The one genuinely useful constraint it could restate (pipe-separated, up to 10 part numbers) is left entirely to the schema.

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 gives a specific verb and resource ('Search parts by part number') plus a concrete result cap ('maximum of 50 parts'), which is more than a tautology. It stops short of distinguishing itself from siblings like post_search_partnumberandmanufacturer or post_search_keyword, so an agent must infer the boundary from the names alone.

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 statement of when to choose this over the keyword or partnumber+manufacturer variants, and no exclusions or prerequisites. Usage is only implied by the endpoint path and the word 'partnumber', leaving the agent to guess the routing.

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