Skip to main content
Glama
Sign In
shopify-multi-mcp

shopify-multi-mcp

by fledgeling-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Get store details

get_shop
Read-only

Retrieves a Shopify store's name, domains, contact email, currency, timezone, and plan so you can inspect or verify individual store configuration.

Instructions

Name, domains, contact email, currency, timezone and plan of one store.

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": {
      "store": "<store>"
    },
    "name": "get_shop"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeYesNo stores are connected yet. Call connect_store first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=false already establish this as a safe, non-open read, so the bar is lower. The description adds useful value by enumerating the returned fields, which matters since there is no output schema, but it says nothing about behavior when no store is connected or when the store identifier is invalid.

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 tight sentence with no filler, and the field list is front-loaded. It reads as a fragment rather than a complete sentence, which slightly hurts clarity but wastes nothing.

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?

With no output schema, listing returned fields is the right compensating move, and that is done. However, for a tool whose schema warns 'No stores are connected yet,' the description should surface the connect_store dependency rather than leaving it buried in a parameter description.

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?

One parameter with 100% schema coverage, so the baseline is 3. 'One store' gestures at the single store argument but adds no format, ID convention, or accepted-value detail beyond the schema.

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?

Names the resource precisely and lists the exact fields returned (name, domains, contact email, currency, timezone, plan) for a single store. The phrase 'one store' implicitly distinguishes it from the sibling list_stores, though the description is a noun fragment with no explicit verb like 'retrieve'.

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?

No statement of when to use this versus list_stores or store_report, and no mention of the precondition that a store must be connected. The only routing hint ('Call connect_store first') lives in the schema, not the description.

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