Skip to main content
Glama

save_business_service

Idempotent

Create or update a saved service by ID. Omitted fields keep their current values. Pass null to clear an optional setting. Review changes with the owner before saving.

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": {
      "id": "<id>"
    },
    "name": "save_business_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameNo
priceNo
colourNo
onsiteNo
visualNo
categoryNo
durationNo
staffIdsNo
noShowFeeNoNo-show fee in minor units. For an upfront payment, the fee cannot exceed the amount collected at booking.
resourcesNo
cardOnFileNo
descriptionNo
rebookWeeksNoWeeks after a visit to email the customer a link to book this service again. Null turns the reminder off.
bufferMinutesNo
showOnWebsiteNo
billingCadenceNo
bookableOnlineNo
depositPercentNo
requirePaymentNo
cancellationFeeNoCancellation fee in minor units. For an upfront payment, the fee cannot exceed the amount collected at booking.
durationMinutesNo
hidePublicPriceNo
requireApprovalNo
cancellationHoursNoHours before the appointment that determine when the cancellation fee applies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / durationMinutes
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 1440,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / rebookWeeks
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 52,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Weeks after a visit to email the customer a link to book this service again. Null turns the reminder off."
      +}
  3. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, non-read-only behavior, so the bar is lower; the description still adds real value by disclosing merge semantics (omitted fields preserved, explicit null clears) that the annotations cannot express. It stops short of noting permission requirements or whether the whole record is validated on save.

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 upsert purpose followed by the semantics that matter most. Nothing is padded and every sentence carries information an agent would otherwise have to guess.

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?

For a 25-parameter upsert with no output schema, the description covers mutation semantics and a safety caution, which is the minimum an agent needs to avoid clobbering data. It remains thin on the many domain-specific fields and on what is returned after saving, so it is adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 25 parameters and only 16% schema description coverage, the description should compensate and largely does not: apart from 'id', no field is named or explained. The generic omitted/null rule does apply uniformly to the ~24 optional fields and is genuinely useful, but constraints on fees, deposit, cadence, and the visual union type are left entirely to an under-documented schema.

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?

States a specific verb pair ('Create or update') and the resource ('a saved service'), keyed by ID, which tells an agent this is an upsert rather than a pure create or update. It doesn't explicitly differentiate itself from similar siblings like save_business_service_area, but the resource noun is precise enough to route correctly.

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?

Patch semantics ('Omitted fields keep their current values', 'Pass null to clear') give strong guidance on how to call it, and 'Review changes with the owner before saving' adds a process caution. However, there is no explicit when-to-use versus alternatives such as remove_business_service or list_business_services, leaving routing to be inferred from the name.

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