Skip to main content
Glama

Create or update a client

save_client

Create a client (brand) or update one by client_id, and optionally turn its white-label health report link on or off. Needs a LocalSchema Pro API key in the request headers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoClient (brand) name. Required when creating; omit to keep it when updating.
reportNotrue turns the client's white-label health report link on, false turns it off. Omit to leave it.
websiteNoBrand website; links every branch to one Organization in the client embed. When updating, omit to keep it or send "" to clear it.
client_idNoUpdate this client. Omit to create one.
contact_nameNoContact person. When updating, omit to keep it or send "" to clear it.
contact_emailNoContact email. When updating, omit to keep it or send "" to clear it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 / client_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/5.0
Behavior3/5

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

Annotations already declare the write/non-idempotent/non-destructive profile, and the description usefully adds the API-key-in-headers requirement and the report-link toggle semantics. It does not cover behavior on partial updates beyond the toggle or any failure modes, so it adds context without fully characterizing the operation.

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?

A single front-loaded sentence with no filler; each clause (create, update-by-id, report toggle, auth requirement) carries distinct information an agent needs before calling.

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?

With no output schema and no required parameters, the description plus the rich schema covers what an agent needs: mode selection, auth, and field-level semantics. Minor gaps remain around update side effects (e.g., clearing fields via empty strings) and response shape, but nothing blocking.

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 six parameters (including create/update and clear-with-empty-string semantics) are already documented in the schema. The description only echoes the client_id create/update split, adding no new parameter detail beyond that baseline.

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?

States specific verbs and resource ('Create a client (brand) or update one by client_id') plus a secondary capability (toggling the white-label health report link). The resource naming clearly separates it from save_location and list_clients without needing to name them.

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 the decisive create-vs-update condition ('update one by client_id', omit to create) and states the auth prerequisite (LocalSchema Pro API key in request headers). It stops short of naming alternatives such as list_clients for reads or save_location for the sibling resource, so no explicit exclusions.

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