Moxie CRM MCP Server

update_calendar_event

Modify calendar event fields such as time, location, attendees, and description to correct or refresh information in Moxie CRM.

Instructions

Update an existing calendar event

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "eventId": "<eventId>"
    },
    "name": "update_calendar_event"
  }
}

Input Schema

Name	Required	Description
`title`	No	New title for the event
`endTime`	No	New end time in ISO-8601 format
`eventId`	Yes	ID of the event to update
`location`	No	New event location
`attendees`	No	Updated list of attendee email addresses
`startTime`	No	New start time in ISO-8601 format
`clientName`	No	Client associated with this event
`description`	No	New event description
`projectName`	No	Project associated with this event

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2Aug 2, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'Update an existing calendar event', which indicates mutation but provides no details about partial vs. full updates, error behavior if the event does not exist, permission requirements, or response format. This is a significant gap 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.

Conciseness4/5

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

The description is a single focused sentence, making it concise and easy to parse. However, it is also under-specified, lacking important behavioral and usage details. Still, for what it does say, there is no waste.

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

Completeness1/5

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

Given the tool has 9 parameters, no output schema, and no annotations, the description is extremely incomplete. It does not explain what the return value is, whether update is partial or full replacement, how errors are handled, or any side effects. For a complex mutation tool, this is wholly inadequate.

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% with each parameter having a clear description (e.g., 'New title for the event'). The tool description adds no extra semantic meaning beyond the schema, so the baseline of 3 is appropriate.

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 'Update an existing calendar event' clearly specifies the verb (update), resource (calendar event), and scope (existing), which distinguishes it from sibling tools like create_calendar_event and delete_calendar_event. It is specific and unambiguous.

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 offers no explicit guidance on when to use this tool versus alternatives. It only implies use for existing events via the word 'existing', but does not state prerequisites, exclusions, or how it differs from create/delete. No context or alternative tools are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.