Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

post_search_keyword

Read-only

Search Mouser Electronics parts by keyword and return up to 50 matching results, with options for paging, record count, and stock or RoHS filters.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
requestYes
versionNoAPI version. Defaults to 1.1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this a safe read operation (readOnlyHint=true, destructiveHint=false), so the description is not carrying the safety burden. It usefully adds the 50-result ceiling, but says nothing about paging behavior over larger result sets, auth requirements, or rate limits, and the raw HTTP route contributes little beyond what the tool name implies.

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?

Two sentences, front-loaded with the search purpose, so it is not padded. However, the leading HTTP route token and the reference to a "Models section below" are scaffolding artifacts that may mean nothing in the agent's actual context and displace more useful guidance.

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 search endpoint with no output schema, the description gives the key operational facts: what is searched, how results are ordered by keyword, and the 50-item ceiling. The nested request wrapper and the version parameter remain undocumented in prose, but the schema covers those fields adequately.

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 50%, so the baseline is 3. The description adds the result cap that contextualizes the 'records' parameter, but its main parameter guidance is a pointer to a "Models section below" rather than explaining the nested SearchByKeywordRequest wrapper or the version parameter itself.

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?

States a specific verb and resource ("Search parts by keyword") plus a concrete scope limit ("maximum of 50 parts"), which is more than a restatement of the name. It stops short of naming or distinguishing itself from the keyword-and-manufacturer or part-number siblings, so the agent must infer the boundary.

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 explicit when-to-use guidance and no mention of when a different search tool (e.g. keyword-and-manufacturer or part-number search) would be preferable. The only usage-adjacent information is the 50-record cap, which is a constraint rather than routing guidance.

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