Skip to main content
Glama

Hail Communication for AI

Create a contact

create_contact

Save a workspace contact with a name and a phone number or email address.

A duplicate phone or email returns 409. Returns the new contact record or an error.

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": {
      "name": "<name>"
    },
    "name": "create_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe contact's name.
emailNoThe address to email this contact at, such as ``ana@example.com``. Give this, ``phone_e164``, or both.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.
phone_e164NoThe number to call or text this contact on, such as ``+14155551234``. Give this, ``email``, or both.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / phone_e164 / anyOf
      Previous value: -[
      -  {
      -    "pattern": "^\\+[1-9]\\d{1,14}$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^\\+[1-9][0-9]{1,14}$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"Email address."New value: +"The address to email this contact at, such as ``ana@example.com``. Give this, ``phone_e164``, or both."
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
    • changedInput schema / properties / phone_e164 / description
      Previous value: -"The contact's phone number with country code, such as ``+14155551234``. Give this, ``email``, or both."New value: +"The number to call or text this contact on, such as ``+14155551234``. Give this, ``email``, or both."
  3. Changed2 schema fields changed
    • changedInput schema / properties / phone_e164 / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "pattern": "^\\+[1-9]\\d{1,14}$",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / phone_e164 / description
      Previous value: -"Phone number in E.164 format, such as ``+14155551234``."New value: +"The contact's phone number with country code, such as ``+14155551234``. Give this, ``email``, or both."
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses the concrete duplicate-handling contract: a duplicate phone or email returns 409. That is real behavioral context an agent cannot derive from the hints, and it is consistent with idempotentHint=false. It stops short of covering other failure modes or permission requirements.

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 with the core action first and the error contract second; nothing is padding. Slightly terse rather than wasteful, and there is no structural clutter beyond incidental indentation.

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 simple single-record create with a full input schema and a declared output schema, the description supplies the required inputs, the duplicate failure signal, and the fact that the new record is returned. Return-value details are correctly left to the output schema; only auth/permission context is missing.

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%, so each parameter is already documented in the schema, including the 'give this, email, or both' constraint on the contact channels. The description only restates the required-field rule and says nothing about llm_model, 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 leads with a specific verb and resource ('Save a workspace contact') and states the minimum identifying fields (name plus a phone number or email address). It is clear what the tool does, but it never names a sibling such as lookup_contact or list_contacts to disambiguate create-vs-read paths.

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?

Usage is implied by the verb and by the statement that at least one of phone or email is needed, which tells the agent when the call is valid. There is no explicit 'use this instead of X' routing and no mention of prerequisites such as verifying the contact does not already exist.

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