Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_search_keywordandmanufacturer

Read-only

Search parts by keyword and manufacturer ID, returning up to 50 matching results with optional stock/RoHS filters and paging.

Instructions

[SearchApi] POST /api/v1/search/keywordandmanufacturer This method is deprecated, please use api/v2/search/keywordandmanufacturer. Search parts by keyword and specific manufacturer. Return a maximum of 50 parts. Please review the SearchByKeywordMfrRequest 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_keywordandmanufacturer"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 two genuinely useful facts beyond that: the operation is deprecated and results are capped at 50 parts. It says nothing about pagination interaction with that cap, rate limits, or authentication requirements.

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?

Four short sentences, front-loaded with the deprecation warning and the core purpose, with no filler. The raw POST path line is somewhat redundant given the tool name but is harmless context.

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 single nested-object parameter with no output schema, the description covers purpose, deprecation, the 50-record cap, and points to where request field details live. It does not describe the response shape or paging semantics, which leaves a small gap for a search tool.

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?

The description adds no parameter meaning at all; it only defers to 'the SearchByKeywordMfrRequest item in the Models section.' With reported schema coverage of 0% at the top level, the description should have compensated by explaining the required keyword, the records/startingRecord paging relationship, or the manufacturerId lookup, but it does not.

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?

States a specific verb and resource ('Search parts by keyword and specific manufacturer'), adds the result cap of 50 parts, and names the replacement endpoint api/v2/search/keywordandmanufacturer. That makes it distinguishable from siblings such as post_search_keyword and post_search_partnumberandmanufacturer without opening any schema.

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?

Explicitly declares the method deprecated and routes the agent to the v2 alternative, which is the strongest possible 'when not to use' signal. It does not explain when this endpoint would still be preferable (e.g., legacy integrations), but the deprecation plus named successor covers the main selection decision.

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