Skip to main content
Glama

Create contact

create_contact

Create a contact (person). Use search_companies for the companyId to link an employer. Enforces the workspace plan limit and validates the company/owner links; the result echoes the operating workspace.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
tagsNoTags for segmentation. Optional.
emailNoThe contact's email address. Optional.
phoneNoThe contact's phone number. Optional.
ownerIdNoUser id of the workspace member who owns this contact. Optional.
jobTitleNoThe contact's job title. Optional.
lastNameNoThe contact's last name. Optional.
companyIdNoCompany id to link this contact to (from search_companies). Optional.
firstNameYesThe contact's first name. Required.
documentRoleNoThe contact's role on sales documents. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / documentRole
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "signatory",
      +        "accountant",
      +        "manager",
      +        "other"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The contact's role on sales documents. Optional."
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / email / anyOf
      Previous value: -[
      -  {
      -    "description": "The contact's email address. Optional.",
      -    "format": "email",
      -    "maxLength": 255,
      -    "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "The contact's email address. Optional.",
      +    "format": "email",
      +    "maxLength": 255,
      +    "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed6 schema fields changed
    • addedInput schema / properties / companyId / description
      Added value: +"Company id to link this contact to (from search_companies). Optional."
    • addedInput schema / properties / email / description
      Added value: +"The contact's email address. Optional."
    • addedInput schema / properties / jobTitle / description
      Added value: +"The contact's job title. Optional."
    • addedInput schema / properties / lastName / description
      Added value: +"The contact's last name. Optional."
    • addedInput schema / properties / ownerId / description
      Added value: +"User id of the workspace member who owns this contact. Optional."
    • addedInput schema / properties / phone / description
      Added value: +"The contact's phone number. Optional."
  5. Changed8 schema fields changed
    • changedInput schema / properties / companyId / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "Company id to link this contact to (from search_companies). Optional.",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / email / anyOf
      Previous value: -[
      -  {
      -    "format": "email",
      -    "maxLength": 255,
      -    "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "The contact's email address. Optional.",
      +    "format": "email",
      +    "maxLength": 255,
      +    "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / firstName / description
      Added value: +"The contact's first name. Required."
    • changedInput schema / properties / jobTitle / anyOf
      Previous value: -[
      -  {
      -    "maxLength": 160,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "The contact's job title. Optional.",
      +    "maxLength": 160,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / lastName / anyOf
      Previous value: -[
      -  {
      -    "maxLength": 120,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "The contact's last name. Optional.",
      +    "maxLength": 120,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / ownerId / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "User id of the workspace member who owns this contact. Optional.",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / phone / anyOf
      Previous value: -[
      -  {
      -    "maxLength": 50,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "The contact's phone number. Optional.",
      +    "maxLength": 50,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / tags / description
      Added value: +"Tags for segmentation. Optional."
  6. Added

TDQS

A3.7/5.0
Behavior4/5

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

With annotations already covering safety (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false), the description adds real value: it enforces the workspace plan limit, validates the company/owner links, and notes the result echoes the operating workspace. It does not mention duplicate handling, which matters given idempotentHint=false, but the quota and validation disclosures are substantive.

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?

Three short sentences, front-loaded with the core action, then the linking prerequisite, then behavioral constraints. No filler, though the behavioral sentence packs several clauses and could be split.

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 create tool with 9 parameters, no output schema, and full schema coverage, the description supplies the missing operational context: plan-limit enforcement, link validation, and what the response echoes. Duplicate/non-idempotent behavior is the one notable gap.

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% across all 9 parameters, so the schema already documents every field including that companyId comes from search_companies. The description adds no syntax, format, or defaulting detail beyond the schema, so the 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?

States a specific verb and resource ('Create a contact (person)') and the parenthetical disambiguates it from create_company and create_lead in the sibling list. It stops short of explicitly naming those siblings as alternatives, but the intent is unambiguous.

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?

Adds a useful workflow prerequisite: 'Use search_companies for the companyId to link an employer.' That is a lookup step, not when-to-use guidance — there is no statement of when to create a contact versus creating a lead or company, and no exclusions or preconditions beyond the company link.

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