WeTrack Enterprise MCP Server

wetrack_update_client

Update a client organisation's details, including contact information, address, and timezone, using the client ID with required name and email to keep records current.

Instructions

Update a client organisation's details.

Args: client_id: The client ID. name: Organisation name (required). email: Primary email (required). phone: Phone number. contact_name: Primary contact person name. contact_email: Contact email. contact_phone: Contact phone. address: Physical address. country: Country name. timezone_id: Timezone integer ID.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`email`	Yes
`phone`	No
`address`	No
`country`	No
`client_id`	Yes
`timezone_id`	No
`contact_name`	No
`contact_email`	No
`contact_phone`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 15, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the burden. It discloses that it's an update operation and lists updatable fields, but doesn't mention any side effects, permissions, or reversibility. It adds some value but lacks depth, so a 3 is justified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded with the main purpose. The parameter list is structured as an Args block, which is easy to scan. There is minimal redundancy, though the purpose sentence could be more detailed.

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?

This is a mutation tool with no annotations but with an output schema. The output schema may clarify return values, but the description doesn't cover prerequisites, side effects, or error conditions. With 10 parameters and only brief descriptions, it feels incomplete for complex usage.

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 0%, so the description must compensate. It provides brief descriptions for each parameter (e.g., 'Organisation name (required)'), adding minor meaning beyond the schema's type and default. However, it doesn't clarify semantic details like format or constraints for fields like timezone_id, so it only partially compensates.

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?

The description clearly states the action ('Update') and the resource ('a client organisation's details'), which is specific and distinguishable from siblings like create_client. However, it does not explicitly differentiate from other update tools, so a 4 is appropriate.

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 implies usage for updating client details, but provides no explicit guidance on when to use this tool versus alternatives like create_client or add_client_members. No exclusions or alternative routing are mentioned, so it is only implicit.

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

Deploy Server