Skip to main content
Glama

Get one store

get_store
Read-onlyIdempotent

Returns everything about one store: where it stands, how the chat did today and in the last 7 days (conversations, cart adds, orders and revenue from chat, handoffs, ratings), billing, its chat settings (colours, greeting, starter questions, tone, add to cart), the optional setup steps, and in dashboard_pages a link that opens each dashboard page for this store. Once the store is live, its settings change on the dashboard, or here after the person confirms. Test chats at try_the_chat use the store's credit like real ones. customer_emails counts the emails waiting in the store's connected mailbox (to answer, and those that need a person), not their text.

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_id": "<store_id>"
    },
    "name": "get_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
store_idYesThe store's store_id (not its name).

Output Schema

NameRequiredDescriptionDefault
nameNo
pagesNo
billingNo
activityNo
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
chat_settingsYes
dashboard_urlNo
optional_stepsNo
plugin_versionNoAs the shop's plugin last reported it.
allowed_domainsNoSites allowed to show the chat. Empty means any site.
customer_emailsNo
dashboard_pagesYes
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

C2.9/5.0
Behavior3/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuine non-obvious context: test chats draw on the store's credit like real ones, and customer_emails counts waiting mailbox emails by category rather than by text. The line "its settings change on the dashboard, or here after the person confirms" is muddled for a readOnly tool and could momentarily make an agent think this call mutates state, but the charitable reading is that changes happen through separate settings tools.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single run-on sentence fragment that concatenates return fields with no headings, no front-loading, and no prioritization. Most of its length restates what the output schema already defines, so the content does not earn its space.

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?

As a read-only tool with full annotation coverage, a fully documented single parameter, and an output schema, it is callable correctly from what is supplied. The description nevertheless spends its budget re-explaining the return payload while omitting the one thing structured data cannot give: when to reach for this versus the sibling list and report tools.

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 at 100% schema coverage, where the schema itself disambiguates store_id from a name. The description adds nothing about the parameter and, given that the output schema exists, spends its words on return fields the schema already declares.

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 everything about one store" states a specific verb and resource, and the enumeration (billing, chat settings, setup steps, dashboard_pages) makes the scope concrete enough to separate it from list_stores. It stops short of a 5 because it never names a sibling or an alternative path for the same data, leaving the contrast implicit.

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 call this versus list_stores, get_report, or the propose/apply settings pair. The only oblique signal is "its settings change on the dashboard, or here after the person confirms," which gestures at an update flow without saying whether this read tool participates in it or which tool actually performs the change.

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