Skip to main content
Glama

Update client

update_client
Destructive

Update a client's notes or active flag. Clients manage their own name, email, and phone in the client portal.

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": {
      "client_id": "<client_id>"
    },
    "name": "update_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
client_idYes
is_activeNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already flag this as a non-read-only, destructive mutation, so the description is not obliged to restate that. It does add useful scope context (client-portal fields are off-limits), but it never explains what setting is_active to false actually does, whether it is reversible, or which permissions are needed — the main behavioral risks for a destructive update.

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 with the mutable-field scope front-loaded and the exclusion note following immediately. Nothing is redundant or padded.

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 destructive mutation with four parameters, no output schema, and thin schema coverage, the definition covers what can be changed but not what happens as a result. Missing are the effect of deactivation, the response shape, and any failure modes — meaningful gaps for a write tool.

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 only 25%, with just business_id documented, and the description partially compensates by naming the two mutable fields and implying is_active maps to an 'active flag'. It adds no semantics for client_id or for the consequences of each field's value, so the low-coverage gap is only partly closed.

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?

Names a specific verb and resource (update a client) and narrows the writable surface to two fields, notes and is_active. The second sentence preempts a likely agent question about name/email/phone, though it does not reference siblings like create_client or get_client by name.

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?

Implied usage is clear enough: call this to change a client's notes or activation state. There is no explicit when-not guidance, no note about when to prefer a different tool, and no mention of prerequisites or side effects that would steer the agent away from misuse.

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