Skip to main content
Glama

Create a store

create_store

Adds a new, empty store to the login's agency, with its own cards, posters and locations: for a client, a second business, or a demo to show a prospect. Then set it up with create_card, create_poster and create_location using the returned store_id. Don't use this to set up a store the login already has: call list_stores first and use the existing store if it's the same business.

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
nameYesStore name in Leal, usually the business or client name, e.g. "Bean There Coffee".
intentNoOptional. One short sentence on what the person asked you to do, e.g. "Set up a stamp card for Ground Up Café". Leal shows it in the person's activity log under Settings → AI agents, so they can see what was done for them. Leave out customer details.
logo_urlNoPublic https URL of the wide logo (PNG, JPEG, WebP, GIF or SVG), e.g. from get_brand_kit.
agency_idNoAgency id from list_stores. Only needed when this login runs several agencies.
store_nameNoPublic name customers see on cards and signup pages, if different from name.
square_logo_urlNoPublic https URL of a square logo or icon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / intent
      Added value: +{
      +  "description": "Optional. One short sentence on what the person asked you to do, e.g. \"Set up a stamp card for Ground Up Café\". Leal shows it in the person's activity log under Settings → AI agents, so they can see what was done for them. Leave out customer details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, open-world write. The description adds real value on top: the store starts empty, a store_id is returned for follow-up calls, and duplicates should be avoided via list_stores. It stops short of stating permission/auth requirements or any limits on how many stores a login can hold, which is the only 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.

Conciseness5/5

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

Three sentences, each doing distinct work: what it creates, what to do next, and when not to use it. The positive case is front-loaded and the guardrail is last, with no filler or restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter creation tool with no output schema, the description covers the essential unknowns: the created object is empty, a store_id is returned and consumed by sibling tools, and duplicate creation is the main failure mode. Combined with the annotations and fully documented schema, an agent has everything needed to call it correctly.

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%, so every parameter including intent, logo_url, agency_id and store_name is already documented in the schema with examples. The description only contributes the notion that store_id comes back from this call; it adds no further meaning about the six input fields, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource ('Adds a new, empty store to the login's agency') and immediately enumerates the use cases — a client, a second business, or a prospect demo. That scope plus the explicit hand-off to create_card/create_poster/create_location separates it cleanly from siblings like list_stores and update_store.

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

Usage Guidelines5/5

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

It gives both sides of the decision: create here when setting up a genuinely new business, but call list_stores first and reuse the existing store if the login already has it. It also names the downstream tools to call after creation, so the agent knows the full workflow rather than just this step.

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