Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

v2_get_search_manufacturerlist

Read-only

Retrieve all manufacturer names from Mouser Electronics to support brand lookup, filtering, and parts sourcing workflows.

Instructions

[SearchApi] GET /api/v2/search/manufacturerlist Get all Manufacturer List. Return Manufacturer Name only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "v2_get_search_manufacturerlist"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The read-only, non-destructive annotations are consistent with the description, so the safety profile is already covered. The description adds one genuinely useful behavioral fact beyond the annotations: only manufacturer names are returned, not full records. It says nothing about result size, ordering, or whether the full catalog is returned unfiltered.

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

Conciseness5/5

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

Two short sentences, front-loaded with the operation and followed immediately by the output constraint. The endpoint path duplicates the name slightly, but nothing is ambiguous or padded.

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 zero-parameter read-only list tool with no output schema, the description covers enough: what it returns and that it returns names only. Minor gaps remain around result volume and ordering, but an agent can call it correctly from this.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly implies a no-argument, whole-list call.

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 ("Get all Manufacturer List") and names the endpoint. It also adds a return-scope detail ("Return Manufacturer Name only"). What it does not do is differentiate itself from the v1 sibling get_search_manufacturerlist, which an agent would have to disambiguate by name/version alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no reference to the sibling search tools (v2_post_search_keywordandmanufacturer, get_search_manufacturerlist). Usage is only implied by the fact that it takes no parameters and returns the whole list.

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