Skip to main content
Glama

Save a location

save_location

Save a business location to the LocalSchema account — create one, or update one by location_id (only the business fields you send change) — and optionally publish it to its hosted embed so the client's site updates without code changes. Needs a LocalSchema Pro API key in the request headers.

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

Input Schema

NameRequiredDescriptionDefault
publishNoPublish to the hosted embed now. Default false (saved as a draft).
businessYesBusiness fields in the same shape as generate_schema (name, businessType, address, openingHours, services, …). When updating, only the fields you send change; address merges field by field, lists are replaced.
client_idNoAssign to a client (see list_clients); null removes the assignment. Omit to keep the current client.
location_idNoUpdate this location. Omit to create a new one (counts toward the plan's location limit).
website_urlNoPage where the hosted embed is installed; health checks scan it. Defaults to business.url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / business / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / client_id / anyOf
      Previous value: -[
      -  {
      -    "$ref": "#/properties/location_id"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "format": "uuid",
      +    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / location_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: partial-update semantics ('only the business fields you send change'), merge behavior (address merges field by field, lists are replaced), the publish side effect on the client's live site, the location-limit cost of creating, and the header auth requirement. None of this contradicts the non-readOnly, non-idempotent, non-destructive hints.

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?

A single front-loaded sentence that puts the core action first, then the create/update branch, then the embed side effect, then the auth requirement. It is dense but every clause carries information; the nested em-dash asides make it slightly harder to scan than an ideal two-sentence split.

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?

For a non-readOnly mutation with a nested object and no output schema, the description covers create vs update, publish, auth, and plan-limit cost. What it omits is what a successful call returns (location id/object) and what happens on validation or limit failures, which an agent would want before deciding how to report results.

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 description coverage is 100%, so all five parameters (including the nested business object and client_id null-removes semantics) are already documented inline. The description restates create-vs-update and publish behavior rather than adding syntax or format detail beyond the schema, so baseline 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?

Names a specific verb+resource (save a business location to LocalSchema) and explicitly splits the two modes: create, or update by location_id. The publish-to-embed side effect is stated, which distinguishes it from siblings like get_location or generate_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?

Gives clear when-to-use guidance: omit location_id to create (and it counts toward the plan's location limit), pass it to update, set publish to push to the hosted embed. It also states the Pro API key prerequisite. It doesn't name a sibling alternative for cases where save_location is the wrong tool, so it stops short of a 5.

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