Skip to main content
Glama

createContact

createContact: Create a new contact for use with domain registrations. Requires authentication. Returns the created contact including its id for assignment to domains (registerDomain registrantId). For .al domains (AKEP): registryAttributes is required, postalCode is required, state is the region not the country, no ';' in street, prefer plain ASCII. For a company use the director or contact person as first/last name, the company as organization, entityType 'Person Juridik Privat', its NIPT/VAT, and the director's ID or passport.

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>",
      "lastName": "<lastName>",
      "email": "<email>",
      "phone": "<phone>",
      "street1": "<street1>",
      "city": "<city>",
      "postalCode": "<postalCode>",
      "country": "<country>"
    },
    "name": "createContact"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name.
emailYesContact's email address.
phoneYesPhone number in '+CC.number' format, e.g. '+1.5551234567'.
stateNoState, province, or region, if applicable.
countryYesCountry as a 2-letter ISO 3166-1 alpha-2 code, e.g. 'US'.
street1YesFirst street address line.
street2NoSecond street address line, if needed.
lastNameYesContact's last name.
firstNameYesContact's first name.
postalCodeYesPostal or ZIP code.
sessionKeyNoSession key (osk_...) returned by checkDeviceLoginStatus. Pass it on every call when logged in via the in-chat device flow; omit when connected via OAuth.
organizationNoOrganization or company name, if any.
registryAttributesNoRegistry-specific fields. REQUIRED for .al (AKEP): entityType, doctype, docnr, and nipt for every entityType except 'Person Natyror'. Omit for other TLDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / registryAttributes
      Added value: +{
      +  "description": "Registry-specific fields. REQUIRED for .al (AKEP): entityType, doctype, docnr, and nipt for every entityType except 'Person Natyror'. Omit for other TLDs.",
      +  "properties": {
      +    "docnr": {
      +      "type": "string"
      +    },
      +    "doctype": {
      +      "type": "string"
      +    },
      +    "entityType": {
      +      "type": "string"
      +    },
      +    "nipt": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed11 schema fields changed
    • addedInput schema / properties / city / description
      Added value: +"City name."
    • addedInput schema / properties / country / description
      Added value: +"Country as a 2-letter ISO 3166-1 alpha-2 code, e.g. 'US'."
    • addedInput schema / properties / email / description
      Added value: +"Contact's email address."
    • addedInput schema / properties / firstName / description
      Added value: +"Contact's first name."
    • addedInput schema / properties / lastName / description
      Added value: +"Contact's last name."
    • addedInput schema / properties / organization / description
      Added value: +"Organization or company name, if any."
    • addedInput schema / properties / phone / description
      Added value: +"Phone number in '+CC.number' format, e.g. '+1.5551234567'."
    • addedInput schema / properties / postalCode / description
      Added value: +"Postal or ZIP code."
    • addedInput schema / properties / state / description
      Added value: +"State, province, or region, if applicable."
    • addedInput schema / properties / street1 / description
      Added value: +"First street address line."
    • addedInput schema / properties / street2 / description
      Added value: +"Second street address line, if needed."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value: the authentication requirement, the fact that an id is returned for later assignment, and the TLD-specific precondition that registryAttributes and postalCode are required for .al.

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?

Purpose and return contract are front-loaded, and the .al rules follow. The AKEP sentence is a dense run-on list, but every clause carries a real constraint rather than padding.

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 13 parameters, a nested registryAttributes object, and no output schema, the description supplies the return contract and the nested-object requirements. Minor gaps remain (nothing about error behavior for rejected .al data), but an agent can invoke it correctly from this description plus the schema.

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

Parameters5/5

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

Despite full schema coverage, the description adds semantics the schema lacks: 'state' is the region not the country, street must not contain ';', prefer plain ASCII, and registryAttributes is required for .al. The company-mapping guidance (director as first/last name, company as organization, entityType 'Person Juridik Privat', NIPT/VAT, docnr) is genuinely non-obvious field-level meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 new contact') and immediately scopes it to its purpose ('for use with domain registrations'), which separates it from generic contact/account creation. It also names the downstream consumer (registerDomain registrantId), so an agent knows why this tool exists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for when this tool applies (before assigning a registrantId to a domain) and detailed conditions for .al/AKEP contacts. It does not name updateContact as the alternative for modifying an existing contact, so there is a small gap in explicit exclusions.

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.