WeTrack Enterprise MCP Server

wetrack_create_client

Create a new client organization by providing its name, contact details, address, country, and timezone to enable project tracking and management.

Instructions

Create a new client organisation.

Args: name: Organisation name e.g. 'Acme Corp'. email: Primary contact email e.g. 'contact@acme.com'. contact_name: Primary contact person name e.g. 'John Doe'. address: Physical address e.g. '123 Tech Park'. phone: Organisation phone number. contact_email: Contact person's email (if different from org email). contact_phone: Contact person's phone. code: Short org code e.g. 'AC'. country: Country name. timezone_id: Timezone integer ID (get from wetrack_list_timezones).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`code`	No
`name`	Yes
`email`	Yes
`phone`	No
`address`	Yes
`country`	No
`timezone_id`	No
`contact_name`	Yes
`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

A3.5/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only lists parameters and the creation verb; it does not mention authentication requirements, duplicate client handling, mandatory validation rules, or what side effects occur beyond creating a record.

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?

The summary sentence is immediate and the Args block is compactly organized. Every parameter entry earns its place by adding examples or clarification, with no redundant prose.

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?

For a 10-parameter creation tool with no annotations and no schema descriptions, the description covers all inputs and references the timezone lookup tool. It still lacks usage differentiation from similar creation/update tools, but the presence of an output schema and complete parameter docs makes it largely sufficient for invoking the tool.

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

Parameters5/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 explain every parameter, and it does. It adds concrete examples, clarifies contact_email vs email, and gives a precise source for timezone_id via wetrack_list_timezones, which is exactly the value needed beyond the 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?

The description clearly states 'Create a new client organisation', which identifies the verb and resource. It is not explicitly differentiated from the sibling wetrack_create_organisation, so it stops short of the highest clarity score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives like wetrack_create_organisation, wetrack_update_client, or wetrack_add_client_members. The only indirect usage hint is 'timezone_id ... get from wetrack_list_timezones', which is a dependency rather than a usage policy.

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

Deploy Server