Skip to main content
Glama
nikan

elorus-mcp

by nikan

update_contact

Update existing contact fields such as company name, contact name, email, phone, VAT number, or notes by providing the contact ID and specifying only the fields to change.

Instructions

Update fields on an existing contact. Only provided fields are changed (PATCH semantics).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe Elorus contact ID to update
emailNoPrimary email address
notesNoInternal notes
phoneNoPrimary phone number
companyNoCompany name
is_clientNoMark as client
last_nameNoLast name
first_nameNoFirst name
vat_numberNoVAT / tax registration number
is_supplierNoMark as supplier
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It mentions PATCH semantics but lacks disclosure on error handling, idempotency, or field restrictions. Insufficient for a mutation tool.

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?

Single sentence with no wasted words, front-loaded with purpose. Excellent conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has 10 parameters and no output schema, but description is very short. Does not explain return value, error behavior, or other context needed for correct usage.

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 baseline is 3. Description adds general PATCH behavior but no additional parameter-specific meaning beyond schema descriptions.

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 the verb 'update' and resource 'existing contact', and specifies PATCH semantics, which distinguishes it from 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?

The description implies the contact must exist but does not explicitly state when to use this tool vs other update tools or when not to use it. No exclusions or alternatives mentioned.

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/nikan/elorus-mcp'

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