Skip to main content
Glama

Add a contact

contact_create

Creates one contact in this organisation's address book: name, company, designation, notes, labels, phone numbers and email addresses. A second contact with the same phone number is not refused.

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": "contact_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFull name, if first/last are not given
notesNo
dryRunNoIf true, validate and return the payload without saving
emailsNo
labelsNoLabels / tags
companyNo
lastNameNo
firstNameNo
designationNo
phoneNumbersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=false, destructive=false, idempotent=false), and the description adds a genuinely non-obvious behavior: duplicate phone numbers are accepted rather than rejected, which tells the agent retries can create dupes. It stops short of saying what happens on invalid input or whether the created contact's identifier is returned.

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?

Two short sentences, front-loaded with the action and resource, with zero filler. The duplicate-number caveat is appended efficiently, though it arrives without any framing that tells the agent what to do about it.

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?

For a 10-parameter mutation tool with weak schema coverage and no output schema, the description leaves real gaps: what is returned, how dryRun behaves, and how name/firstName/lastName interact. The duplicate-acceptance note is valuable, but overall it is under-specified for the tool's complexity.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 10 parameters and only 30% schema description coverage, the description should carry more weight, but it merely restates seven field names already visible in the schema. It says nothing about dryRun, the firstName/lastName versus name split, phone-number format expectations, or that no parameter is required.

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?

A specific verb plus resource ('Creates one contact in this organisation's address book') followed by an enumeration of the settable fields, so an agent knows exactly what the tool produces. It does not distinguish itself from siblings such as contact_update or lead_create, which is the only thing keeping it from a 5.

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 'one contact' phrasing and the address-book scope imply this is the single-record creation path rather than bulk import, but there is no explicit guidance on when to reach for contact_update or lead_create instead. No prerequisites or authentication requirements are stated.

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.