Create a new client profile and property in Jobber CRM.
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | Property city. | |
| No | Client email address. | ||
| phone | No | Client phone number. | |
| street | No | Property street address. | |
| lastName | Yes | Last name of the client. | |
| province | No | Property state/province. | |
| firstName | Yes | First name of the client. | |
| postalCode | No | Property ZIP or postal code. | |
| companyName | No | Company name if applicable. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without revealing side effects (e.g., duplicate client handling, automatic property creation), permission requirements, or output behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no filler, front-loading the action and subject. It is appropriately sized for the minimal information it conveys.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with 9 parameters, no output schema, and no annotations, the description is too sparse. It does not explain what happens after creation, what is returned, or any constraints beyond the input schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description itself adds no parameter-level detail beyond what the schema already provides, though it does give high-level context of creating both a client and property.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action (create), resource (client profile and property), and system (Jobber CRM). It is easily distinguishable from sibling tools like jobber_create_job and jobber_create_quote.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, such as jobber_search_clients for existing clients or jobber_create_job for jobs. No prerequisites or selection criteria are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.