Skip to main content
Glama
Sign In
mouser-mcp

mouser-mcp

by bradford-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Mouser countries

list_countries
Read-onlyIdempotent

Retrieves the countries and states that Mouser ships to, optionally filtered by a country code, so you can validate shipping destinations before ordering.

Instructions

Countries (and their states) Mouser ships to, optionally for one country code.

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": "list_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryCodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.5

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that each country carries its states and that the filter is optional, but says nothing about ordering, pagination, or response size for what is an open-world read.

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?

A single efficient sentence with the resource front-loaded and the optional modifier clearly attached. Nothing is wasted, though it is terse enough that added format detail would not have hurt.

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 simple parameterless-filter list tool with no output schema and annotations covering safety, the definition is close to adequate. It still omits country code format and any hint about the shape of returned country/state data, which an agent must infer.

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 0%, so the single countryCode parameter is undocumented in the schema. The description clarifies that it narrows results to one country, but does not state the expected format (e.g. ISO alpha-2) or what happens when omitted, leaving a gap for the only parameter.

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 resource (countries and their states that Mouser ships to) with a clear scope, and the optional filter is named. It doesn't distinguish itself from siblings like list_currencies, so it stops short of a 5, but its purpose is unambiguous.

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?

The phrase 'optionally for one country code' implies the caller can either enumerate all countries or narrow to one, which is implied usage guidance. There is no explicit when-to-use guidance or mention of alternatives such as list_currencies for a related lookup.

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

Deploy Server

Other Tools