Skip to main content
Glama

List stores

list_stores
Read-onlyIdempotent

Lists the Emporiqa stores this person owns, with where each one stands, its last 7 days, its billing (spend this month, credit left, card, monthly cap) and its next step. Stores the person belongs to but does not own are listed separately; only their owner can set those up. Only the newest 25 are listed; total_owned then gives the count, and name filters the list.

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

Input Schema

NameRequiredDescriptionDefault
nameNoOnly stores whose name contains this.

Output Schema

NameRequiredDescriptionDefault
listedNoWith total_owned: how many are listed here.
storesYes
total_ownedNoPresent when the list is cut at 25: how many stores match in all.
account_emailYes
stores_owned_by_someone_elseNo
stores_needing_another_sign_in_methodNo

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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavioral context beyond them: a hard cap of 25 results, the total_owned counter to recover the true count, and ownership-based result partitioning. It does not say what ordering "newest 25" uses, which is the main remaining gap.

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 sentences, front-loaded with what is listed and the ownership scope, then the pagination and filter caveats. The middle clause enumerating return fields (standing, last 7 days, billing, next step) is dense but serves selection rather than padding.

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?

An output schema exists, so return values needn't be detailed, and the description still covers scoping, the 25-item cap, the count field, and filtering. What an agent needs to call it correctly is present; only result ordering is unspecified.

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 coverage is 100% and the single parameter already documents substring matching on name. The description's "name filters the list" restates that without adding syntax, case-sensitivity, or matching details, so it sits at the baseline for a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Lists the Emporiqa stores this person owns") plus the scope: only owned stores, with member stores handled separately. An agent can distinguish this from get_store or create_store without opening any schema.

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?

Explains the owned-vs-member split and notes that only an owner can set up member stores, which implicitly routes non-owners elsewhere. It does not name a concrete alternative tool for that case, so the routing is left partly to inference rather than stated explicitly.

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