Skip to main content
Glama
philipp-mlr

monica-mcp

by philipp-mlr

monica_conversation

List, create, update, and delete conversations. Also manage messages within conversations by adding, updating, or deleting them. Organize communication history.

Instructions

Manage conversations. Actions: list, get, create, update, delete. ⚠️ delete is irreversible. Additional actions: list_messages, add_message, update_message, delete_message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoEntity ID (required for get/update/delete)
pageNoPage number
limitNoPage size (max 100)
actionYesOperation to perform: list | get | create | update | delete | list_messages | add_message | update_message | delete_message. "list" = paginated list, "get" = by ID, "create" = new record, "update" = modify by ID, "delete" = remove by ID (irreversible).
contact_idNoContact ID
message_idYesMessage ID to delete
written_atNoWhen written (YYYY-MM-DD)
written_by_meNoWhether written by me
message_contentYesUpdated message content
conversation_contentNoInitial message content
contact_field_type_idNoContact field type ID (channel)
Behavior2/5

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

The description only mentions that delete is irreversible. Given no annotations, it should disclose more behavioral traits such as side effects of other actions, required permissions, rate limits, or idempotency. The current disclosure is minimal.

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?

The description is concise, consisting of two sentences. However, given the complexity of 11 parameters and 9 actions, it could be better structured to quickly convey required parameter combinations per action.

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 description lacks explanation of usage patterns, required parameter combinations for each action, and common workflows. Without output schema or annotations, the agent is left to infer how to invoke actions correctly, leading to potential errors.

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?

All parameters have descriptions in the input schema (100% coverage), so the baseline is 3. The tool description does not add any further semantic value beyond what the schema already provides.

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 states the resource ('conversations') and lists multiple actions, making the tool's purpose clear. However, it does not differentiate from sibling CRUD tools like monica_contact or monica_note, which likely have similar action patterns.

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?

No guidance is provided on when to use this tool versus alternatives. The only conditional advice is a warning about irreversible delete, but there is no information about prerequisites, context, or when not to use the tool.

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