Skip to main content
Glama
Mouser MCP

Mouser MCP

by RainnWorks

get_order_countries

Read-only

Retrieve the countries and state/province lists available for orders, with optional filtering by country code, to populate address forms and validate order destinations.

Instructions

[Order] GET /api/v{version}/order/countries Returns a list of countries plus any state/provinces the countries have.

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

Input Schema

NameRequiredDescriptionDefault
versionNoAPI version. Defaults to 1.1
countryCodeNoOptional. Allows the country list to be filtered by country code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 structurally. The description adds genuine value by disclosing the return payload includes nested state/province data, but it says nothing about pagination, result size, ordering, or whether the list is cached/static — context that would matter for a reference endpoint.

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?

Two compact lines: a bracketed domain tag plus route, then a single sentence describing the return. It is front-loaded and wastes no words, though the raw route string is boilerplate rather than explanatory content.

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?

There is no output schema, so the description's sentence about returning countries plus their states/provinces is doing real work in telling the agent what comes back. Combined with full schema coverage and read-only annotations, that is nearly complete for a simple two-optional-param lookup; only the filter behavior and result-size characteristics are missing.

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 100%, so both parameters (version with its default, countryCode with its filter meaning) are fully documented in the schema; the baseline is 3. The description adds no parameter meaning beyond that — notably it never mentions the countryCode filter, which is the one behavioral nuance worth surfacing here.

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?

"Returns a list of countries plus any state/provinces the countries have" states a specific verb (returns a list) and a specific resource (countries with nested states/provinces), and the route line confirms it is a read lookup. It is clearly distinguishable from siblings like get_order_currencies or get_order_by_ordernumber by resource alone, though it never explicitly names an alternative.

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?

Usage is only implied: the tool is evidently a reference-data lookup for country/state lists, but the description gives no explicit when-to-use condition, no prerequisites, and no guidance on choosing it over sibling lookups. An agent can infer the use case from the resource name, which is the definition of minimum viable.

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