Skip to main content
Glama

Add a store location

create_location

Adds a physical location to a store. The address is geocoded so wallet passes can remind customers nearby.

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>",
      "address": "<address>"
    },
    "name": "create_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYese.g. "Main Street" or the store name for a single shop.
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.
addressYesFull street address including town and postcode.
store_idNoStore id from list_stores. Optional when the login has one store.

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

A3.8/5.0
Behavior4/5

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

Annotations already flag non-read-only, non-idempotent, non-destructive behavior, so the bar is lower. The description still adds genuinely new context: the address is geocoded and this feeds wallet-pass proximity reminders, meaning an invalid or incomplete address has downstream effects. It stops short of covering duplicate-location handling or failure behavior when geocoding fails.

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?

Two short sentences, no filler, purpose first and the geocoding consequence second. Every clause carries information an agent needs.

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?

Parameters and safety are well covered by the schema and annotations, but with no output schema the description should say what comes back after creation (e.g. a location id or confirmation) and it does not. There is also no mention of what happens on duplicate addresses or a failed geocode, which matters for a non-idempotent mutation.

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 baseline is 3. The description adds meaning beyond the schema by explaining that the address is geocoded and used for proximity reminders, which tells the agent the address must be precise and complete — a semantic constraint the schema's "Full street address including town and postcode" only partially conveys.

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?

The description gives a specific verb and resource ("Adds a physical location to a store") and adds a second-order consequence (geocoding so wallet passes can remind nearby customers). It does not distinguish itself from siblings such as create_store, so an agent must infer from the name that this is a sub-resource of an existing store rather than a new store.

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

Usage Guidelines3/5

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

The implication is that this is used when adding a branch/shop to an existing store, and the schema notes store_id comes from list_stores, but the description itself states no when-to-use rule, no precondition (does the store need to exist first?), and no alternative to consider. Usage is only inferable, not stated.

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