Skip to main content
Glama

save_business_location

Idempotent

Create or edit a business location. Omitted address, phone, staffIds and active fields keep their current values when editing. Pass an empty staffIds array to allow all staff. Set active to false to stop offering it for booking. Reuse the same idempotency key on retry.

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": {
      "location": "<location>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "save_business_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationYes
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (which only cover safety and idempotency), the description discloses the partial-update semantics — omitted address, phone, staffIds and active retain current values — plus two non-obvious side effects: empty staffIds means all staff and active=false disables booking. The retry guidance also explains the practical purpose of idempotencyKey rather than just restating idempotentHint.

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?

Four short sentences, front-loaded with the core action and followed by the highest-risk edge cases. Every sentence carries operational information; nothing restates the tool name or the schema.

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 mutating nested-object tool with no output schema and no field descriptions in the schema, the description covers the semantics an agent most needs. It stops short of saying what happens when an unknown id is supplied or whether an edit returns the saved record, which matters for a create-or-edit tool.

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 0%, so the description must carry parameter meaning, and it does for staffIds, active, address, phone and idempotencyKey, including the subtle omit-vs-empty distinction. Gaps remain: it never explains the nested id field's role in switching create vs edit, and it gives no hint on how to clear a field that is omitted-by-default.

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?

"Create or edit a business location" gives a concrete verb pair plus resource, and the upsert framing (id present = edit, absent = create) is inferable. It does not name or contrast with siblings like save_business_brand or list_business_locations, but the resource is specific enough to distinguish it.

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 description frames the tool as the write path for locations and gives concrete operating conditions (omit fields to preserve them, empty staffIds for all staff, active=false to stop bookings). It never explicitly states when to prefer this over siblings such as get_business_location or list_business_locations, nor how to obtain an existing location id.

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