Skip to main content
Glama

update_contact

Find a contact by ID or name and update their details including name, organization, phone, email, and notes.

Instructions

Update a unique Contacts record by id or name match.

Args: identifier: Contact id or name text first_name: Optional replacement first name last_name: Optional replacement last name organization: Optional replacement organization/company phone: Optional phone number to add email: Optional email address to add note: Optional replacement note

Returns: Structured JSON with the updated contact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
emailNo
phoneNo
last_nameNo
first_nameNo
identifierYes
organizationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description must disclose behavioral traits. It states update operation and returns updated contact, but does not address handling of multiple name matches, permissions, or side effects. Could be more transparent.

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 sentences plus clean arg list. Purpose stated upfront, concise. Well-structured.

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 output schema available, description sufficiently covers input parameters and return value. Lacks error handling or edge cases, but adequate for basic usage.

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

Parameters4/5

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

Schema description coverage is 0%, so description compensates by listing all 7 parameters with brief explanations. Adds meaning beyond type and default values, though could include format constraints.

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?

Clearly states 'Update a unique Contacts record by id or name match.' Specific verb and resource, distinct from sibling tools like create_contact and get_contact.

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?

No explicit guidance on when to use this vs alternatives like create_contact or search_contacts. Usage is implied from the description, but lacks when-not or context differentiation.

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