get_store_infoRetrieve store regions, currencies, sales channels, and stock locations. Use this first call to get location IDs and currencies before managing orders, products, or inventory.
Returns regions (currencies), sales channels and stock locations. A good first call to learn location IDs and currencies.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds that this is a discovery call and enumerates returned categories, but nothing about pagination, auth, or failure modes, which is minor for a static lookup.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences: the first lists the returned data, the second gives the actionable cue. Nothing is wasted and the important framing is not buried.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-param, read-only overview tool with no output schema, describing the returned categories is sufficient for an agent to call it correctly. Slightly more detail on the response shape would help, but the essentials are present.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing to disambiguate; baseline for a parameterless tool is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (returns) plus the exact resources it exposes: regions/currencies, sales channels, and stock locations. It is distinguishable from list-oriented siblings, though it does not name them explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says it is 'a good first call to learn location IDs and currencies,' which tells an agent when to prefer it — bootstrap/discovery. No when-not conditions or named alternatives, but the usage context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.