Skip to main content
Glama

Create a store

create_store

Creates a new Emporiqa store on this account. It starts with free signup credit and needs no card. With platform, the result includes that platform's install steps. If a store with the same name exists, it is returned instead, unless confirm_new is true.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe shop's name.
platformNoWhat the shop runs on, if known.
confirm_newNoTrue creates a second store even when one with this name exists.

Output Schema

NameRequiredDescriptionDefault
nameNo
thenNoThe next step.
pagesNo
billingNo
createdYes
installNo
platformNo
productsNo
store_idYes
chat_liveNoShoppers are chatting on the shop: it has been seen there and nothing pauses it.
next_stepNo
billing_urlNo
chat_statusNoA one-line plain status.
last_7_daysNoNull until the shop is connected.
connected_atNo
dashboard_urlNo
plugin_versionNoAs the shop's plugin last reported it.
allowed_domainsNoSites allowed to show the chat. Empty means any site.
already_existedNo
plugin_connectedNoThe shop's plugin has reached Emporiqa at least once.
last_data_received_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing the name-collision behavior (existing store returned instead of a new one unless confirm_new is true), the free credit/no-card condition, and that platform adds install steps to the response. It does not cover permissions or any rate/limit behavior, which for a creation tool would round this out.

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?

Four short sentences, front-loaded with the verb and resource, then the incentive, then platform behavior, then the collision rule. Nothing is redundant with the title or restated needlessly.

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?

With an output schema present and full annotation coverage, the description need not explain return values, and it fills in the non-obvious dedup behavior. The only gap is operational context such as permissions or what happens to the account's billing state beyond the free credit mention.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns an extra point by explaining the consequence of 'platform' (install steps included in the result) and the default collision semantics governed by 'confirm_new'. The parameter-level descriptions already carry the core meanings, so the description adds consequence rather than definition.

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 ('Creates a new Emporiqa store on this account') and immediately scopes it to this account. It does not explicitly distinguish itself from the sibling 'set_up_store', so an agent must infer the split between creating a store and setting one up.

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

Usage Guidelines4/5

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

Gives clear context for the call: free signup credit, no card required, and that supplying a platform yields install steps in the result. It offers no explicit exclusions or pointers to sibling tools such as set_up_store or get_install_steps, leaving alternative selection to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources