meshbook-mcp

create_contact

Create a CRM contact in the active mesh using a first and last name, with optional email and company. The server resolves free-text company names to existing companies where possible.

Instructions

Create a CRM contact in the active mesh. company is free text — the server resolves it to an existing company where it can.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`email`	No
`company`	No
`last_name`	Yes
`first_name`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 12, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it discloses one genuinely non-obvious behavior: 'company' is free text and the server resolves it to an existing company when possible. This is valuable, but it omits permissions, duplicate handling, and side effects for a mutation tool.

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 tightly written sentences, front-loading the core purpose and then the one parameter caveat. No wasted words.

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?

An output schema exists, so return values need no explanation. However, for a mutation tool with no annotations and zero schema coverage, the description should say more about failure modes, required permissions, or duplicate behavior to be fully complete.

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 coverage is 0%, so the description must compensate. It explains the least obvious parameter ('company' free-text resolution), which is the highest-value gap, but first_name, last_name, and email receive no added semantics, so compensation is only partial.

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?

States a specific verb and resource ('Create a CRM contact') plus the scoping context ('active mesh'), so the agent knows what operation it performs. It does not explicitly distinguish itself from the sibling create_lead, leaving a minor ambiguity between the two creation tools.

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?

No when-to-use guidance is given. There is no indication of when to create a contact versus the sibling create_lead, nor any prerequisites or conditions for use.

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