Skip to main content
Glama
philipp-mlr

monica-mcp

by philipp-mlr

monica_contact

Manage contacts with actions: list, get, create, update, delete, search, set tags, update career, and view associated activities, calls, notes, tasks, reminders, and more.

Instructions

Manage contacts. Actions: list, get, create, update, delete. ⚠️ delete is irreversible. Additional actions: search, set_tags, update_career, list_activities, list_calls, list_addresses, list_notes, list_tasks, list_reminders, list_gifts, list_debts, list_relationships, list_conversations, list_photos, list_documents, list_fields, list_audit_logs, assign_tag, remove_tag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoEntity ID (required for get/update/delete)
jobYesJob title
pageNoPage number
sortNoSort: created_at, -created_at, updated_at, -updated_at
tagsYesArray of tag names to set
limitNoPage size (max 100)
queryNoSearch query (searches name, nickname, email, job, company)
actionYesOperation to perform: list | get | create | update | delete | search | set_tags | update_career | list_activities | list_calls | list_addresses | list_notes | list_tasks | list_reminders | list_gifts | list_debts | list_relationships | list_conversations | list_photos | list_documents | list_fields | list_audit_logs | assign_tag | remove_tag. "list" = paginated list, "get" = by ID, "create" = new record, "update" = modify by ID, "delete" = remove by ID (irreversible).
tag_idYesTag ID to remove
companyYesCompany name
nicknameNoNickname
birthdateNoBirthdate (YYYY-MM-DD)
gender_idNoGender ID
last_nameNoLast name
first_nameNoFirst name
is_partialNoWhether this is a partial contact
is_deceasedNoWhether contact is deceased
birthdate_ageNo
deceased_dateNo
food_preferenciesNo
is_birthdate_knownNoWhether birthdate is known
birthdate_is_age_basedNo
is_deceased_date_knownNoWhether deceased date is known
stay_in_touch_frequencyNo
birthdate_is_year_unknownNo
Behavior3/5

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

No annotations are provided, so the description carries full burden. It warns that 'delete is irreversible' using a warning symbol, which is good. However, it does not disclose other behaviors like read/write safety, rate limits, or side effects of other actions.

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

Conciseness3/5

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

The description is front-loaded with 'Manage contacts,' but then becomes a long enumeration of actions. It is somewhat verbose but structured with a warning and two lists. Could be more concise by grouping similar actions.

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?

The tool has 25 parameters and no output schema. The description lacks information about data model, parameter dependencies, and action-specific requirements. For example, 'update_career' is listed but not explained. Pagination and sorting are partially covered in schema but not in description.

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 76%, which is high. The description lists actions but adds little meaning beyond the schema's parameter descriptions. It does not elaborate on parameter usage or constraints beyond what schema already provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with 'Manage contacts,' which clearly identifies the resource. The list of actions (list, get, create, update, delete) provides specific verbs. However, the description is more of a menu than a concise verb-resource statement, lacking a focused purpose. It distinguishes from siblings by targeting contacts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives. It lists actions but does not explain context or trade-offs. No sibling comparison or situational advice is given.

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/philipp-mlr/monica-mcp'

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