MightyAutomation

Create an appointment

create_appointment

Add an appointment, call, or meeting to the workspace Sales Calendar, optionally attached to a contact (by contact_id or email). This writes the CRM calendar only — it does not create a Google Calendar event, send an invite, or email anyone.

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": {
      "title": "<title>",
      "scheduled_at": "<scheduled_at>"
    },
    "name": "create_appointment"
  }
}

Input Schema

Name	Required	Description
`type`	No	Kind of event (default appointment).
`email`	No	The contact email address. Use to locate a contact when you do not have its id, or to set a new email on update_contact.
`notes`	No	Internal notes on the appointment.
`title`	Yes	Appointment title.
`location`	No	Location text (address, phone number, or room).
`contact_id`	No	The contact id (uuid) from find_contact / list_contacts / search_leads.
`meeting_url`	No	Video meeting link, if any.
`scheduled_at`	Yes	ISO 8601 start time with an offset, e.g. 2026-11-03T14:00:00-07:00.
`duration_minutes`	No	Length in minutes, 5-480 (default 30).

Output Schema

Name	Required	Description
`ok`	No
`error`	No	Present only when ok is false.
`appointment`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare non-readonly, non-destructive, non-idempotent, so the description's real contribution is the side-effect boundary: CRM calendar write only, no external invite or email. That is valuable context an agent cannot get from the annotations. It does not warn about duplicate records on retry despite idempotentHint=false, which is the one notable behavioral gap.

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?

Two sentences, zero filler, with the core action and target front-loaded before the negative scope clause. Every clause carries a constraint the agent needs.

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

Completeness4/5

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

With an output schema present and annotations covering the safety profile, the description fills the remaining need — scope and side effects — adequately. Minor gaps remain around duplicate/retry behavior and what happens if the contact cannot be resolved, but nothing blocking for a 9-parameter create tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3; the description adds meaning by explaining that contact attachment is optional and can be done via contact_id or email, clarifying the relationship between those two schema fields. It still doesn't explain how type or duration_minutes defaults interact with required fields.

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?

States a specific verb (Add) and resource (appointment, call, or meeting) plus the exact target (workspace Sales Calendar), and scopes it against adjacent concepts like Google Calendar events and invites. An agent can distinguish this from list_appointments, cancel_appointment, reschedule_appointment, and create_booking_link without opening a schema.

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

Usage Guidelines4/5

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

The second sentence gives a clear when-not: it does not create a Google Calendar event, send an invite, or email anyone, which tells the agent not to expect notification side effects. It stops short of naming sibling alternatives (e.g. create_booking_link for a self-serve scheduling link) or prerequisites for contact lookup.

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

All MightyAutomation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?