Skip to main content
Glama

Save Contact

save_contact
Idempotent

Create or update a reusable contact profile for domain registration and management. Saved contacts can be referenced when registering or updating domain contacts.

Instructions

Create or update a reusable contact profile. Saved contacts can be referenced when registering domains or updating domain contacts. If a contactId is provided, the existing contact is updated; otherwise a new contact is created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
faxNoFax number in E.164 format
cityYesCity name
emailYesEmail address of the contact
phoneYesPhone number in E.164 format (e.g. +1.5551234567)
faxExtNoFax extension number
countryYesISO 3166-1 alpha-2 country code (e.g. US, DE, NL)
address1YesPrimary street address
address2NoSecondary address line (apt, suite, etc.)
lastNameYesLast name of the contact
phoneExtNoPhone extension number
contactIdNoUnique contact identifier (omit when creating a new contact)
firstNameYesFirst name of the contact
taxNumberNoTax identification number
postalCodeNoPostal or ZIP code
organizationNoOrganization or company name
stateProvinceNoState or province name/code
Behavior4/5

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

Description adds context that contacts are reusable and references domain operations. Annotations already indicate idempotency and non-destructiveness; description aligns and adds value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences: first explains overall purpose and usage context, second specifies the create/update distinction. No unnecessary words.

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 many parameters and no output schema, the description adequately explains the core behavior (create/update, reusability). Missing details on return values or error scenarios, but acceptable for a CRUD tool.

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 coverage is 100%, so all parameters are documented. Description adds the key context that contactId determines create vs update, but does not elaborate on other fields beyond the schema.

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?

Description clearly states the tool creates or updates a reusable contact profile, and explains it can be referenced for domain registration/updates. This differentiates it from siblings like get_contact and save_contact_attributes.

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?

Clearly specifies when to create (no contactId) vs update (with contactId). Implies use when needing a reusable contact for domain operations, but does not explicitly state when not to use (e.g., for one-time contacts).

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/BartWaardenburg/spaceship-mcp'

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