Skip to main content
Glama

create_contact

Create a contact record with required first and last names and optional details like organization, phone, email, and note.

Instructions

Create a Contacts record with optional organization, phone, email, and note.

Args: first_name: Contact first name last_name: Contact last name organization: Optional organization/company phone: Optional phone number to add with mobile label email: Optional email to add with home label note: Optional contact note

Returns: Structured JSON with the created contact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
emailNo
phoneNo
last_nameYes
first_nameYes
organizationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations exist, so the description carries full burden. It only states creation but does not disclose potential side effects, ID generation, or whether existing contacts are checked. No contradiction with annotations.

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?

The description is concise with clear Args and Returns sections. Every sentence adds value. Minor redundancy: defaults in schema could be inferred, but not burdensome.

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?

Given the tool has an output schema (though not provided), the description adequately describes return as 'Structured JSON with the created contact'. Parameter descriptions are complete for required and optional fields.

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?

Schema description coverage is 0%, so the description's parameter list is essential. It adds meaning: e.g., 'optional organization/company', 'optional phone number to add with mobile label', and 'optional email to add with home label'. This contextualizes the parameters beyond the schema's type/default.

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?

The description clearly states 'Create a Contacts record' and lists specific optional fields. It distinguishes from sibling tools like update_contact, get_contact, and search_contacts by focusing on creation.

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 description implies use when creating a new contact but does not explicitly state when to use alternatives or conditions for use. No exclusion criteria or when-not-to-use guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/altic-dev/altic-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server