Skip to main content
Glama

HonestCRM

Create a contact

create_contact

Create a contact. Counts toward the workspace's contact limit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoJob title, such as Head of Sales.
customNoCustom field values as an object of custom field id to value.
emailsNoEmail addresses. The first one is the primary address.
phonesNoPhone numbers. The first one is the primary number.
tagIdsNoIds of tags to attach (at most 20).
lastNameNoLast name.
companyIdNoThe id of the company the contact works for. Use search to find it.
firstNameNoFirst name.
ownerUserIdNoThe id of the user who owns the contact. Default: the signed-in user.
leadSourceIdNoThe id of the lead source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds genuinely new information beyond annotations by warning that the call counts toward the workspace's contact limit, which implies a finite quota. However, it says nothing about duplicate detection, what happens when the limit is reached, or permissions needed.

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 short sentences with zero filler, and the core purpose is front-loaded before the quota caveat. Every sentence carries information an agent would not otherwise have.

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 10 optional parameters, a nested custom-field object, no output schema, and full schema coverage, the description covers purpose and the quota caveat adequately. It leaves a minor gap in not indicating what a successful call returns (e.g., the new contact id) or how to handle near-duplicate contacts.

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%, and the parameter descriptions already explain semantics such as the first email being primary, defaults for ownerUserId, and pointing to search for companyId. The description adds no parameter-level meaning beyond that, so baseline 3 applies.

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 states a specific verb and resource ("Create a contact") that unambiguously matches the tool name and title. It does not differentiate from siblings such as create_company or update_contact, but the create-a-contact framing is clear enough on its own.

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 when-to-use guidance, no mention of alternatives (e.g., update_contact for existing records, search to check for duplicates first), and no prerequisites such as required company or owner lookups. The agent must infer all usage context from the schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources