Skip to main content
Glama
mnicole-dev

@mnicole-dev/erezo-mcp-server

by mnicole-dev

create_contact

Create a new professional contact in your network, storing details like company, email, status, notes, and next actions. Track follow-ups, recommendations, and preferred channels.

Instructions

Create a new contact. Subject to quota limits (freemium: 20 max, premium: 30/day).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoJSON array of tags, e.g. ["tech", "startup"]
emailNoEmail address
notesNoFree-text notes
phoneNoPhone number
statusNoContact status (default: network)
addressNoPostal address
companyNoCompany name
birthdayNoBirthday (YYYY-MM-DD)
lastNameYesLast name (required)
firstNameYesFirst name (required)
interestsNoJSON array of interests
languagesNoJSON array of language codes, e.g. ["fr", "en"]
nextActionNoNext action to take
professionNoJob title / profession
trustLevelNoTrust level: 1=New, 2=Emerging, 3=Established, 4=Strong, 5=Total
websiteUrlNoWebsite URL
meetingDateNoWhen you met (ISO 8601 date-time)
meetingPlaceNoWhere you met this person
nextActionDateNoDeadline for next action (YYYY-MM-DD)
isRecommendableNoWhether this contact can be recommended
potentialRevenueNoPotential revenue in euros
preferredChannelNoPreferred communication channel
opportunityStatusNo1=Opportunity, 2=To explore, 3=Not interesting
recommendationNoteNoNote about recommendation
Behavior3/5

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It does add useful context by revealing quota limits (freemium: 20 max, premium: 30/day). However, it does not disclose other important traits such as idempotency, duplicate handling, required fields, or what the response contains.

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?

The description is extremely concise, composed of two short sentences. The key action is front-loaded, and the quota information is the only extra detail, earning its place.

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

Completeness3/5

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

Given the tool has 24 parameters, no annotations, and no output schema, the description is a bit thin. It does not mention what is returned on success, failure behavior, or required fields (though the schema covers required fields). It is adequate but minimal for a complex creation 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 description coverage is 100%, so the baseline is 3. The description does not add any parameter-level meaning beyond the schema; it only mentions quota limits, which are not parameter semantics.

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 states the specific verb and resource: 'Create a new contact.' This clearly distinguishes it from sibling tools like update_contact, get_contact, list_contacts, and delete_contact, which all have different actions on the same resource.

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 gives contextual guidance by mentioning quota limits, which implies when the tool cannot be used (when quota is exhausted). However, it does not explicitly state when to choose this tool over alternatives or mention any exclusion criteria.

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/mnicole-dev/erezo-mcp-server'

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