Veterical Vet Clinic

Update a pet owner's details

update_client

DestructiveIdempotent

Use this when someone asks to change a pet owner's name, phone, email or language. Returns the owner's id, name, clinic and which fields changed; contact details are never returned. Not for changing an animal's details.

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

Input Schema

Name	Required	Description
`name`	No	New full name.
`email`	No	New email address.
`phone`	No	New mobile number, with the country code when known.
`clientId`	Yes	Id of the owner, from find_client.
`language`	No	New language for their messages, as a code such as en or it.
`expectedLastEditTime`	Yes	The lastEditTime from find_client. An owner changed since then is refused.

Output Schema

Name	Required	Description	Default
`client`	Yes
`status`	Yes
`changedFields`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=true and openWorld=false, so the safety profile is covered. The description adds that the call returns the owner's id, name, clinic and changed fields, and that contact details are never returned — a useful privacy behavior not present in the annotations.

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 sentences with zero filler: the use condition and the return shape come first, then the exclusion. Nothing is repeated from the schema descriptions.

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 an output schema present and full schema coverage, the description need only say what to call it for and what comes back, which it does. It leaves the optimistic-concurrency workflow (obtaining expectedLastEditTime from find_client) to the schema, which is acceptable but means the description alone doesn't convey the retry implication.

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 every parameter including clientId and expectedLastEditTime is already documented in the schema. The description only echoes the editable field list (name, phone, email, language) and adds no format or constraint detail beyond that.

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 ('change a pet owner's name, phone, email or language') and enumerates the editable fields, so the scope is unambiguous. It also explicitly excludes animal records, which cleanly separates it from the sibling update_patient.

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 an explicit triggering condition ('Use this when someone asks to change...') plus an exclusion ('Not for changing an animal's details'), which routes the agent toward update_patient. It stops short of naming that sibling or stating prerequisites such as fetching the current record first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Veterical Vet Clinic tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?