Skip to main content
Glama
chrischall

evite-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

evite_create_event

Create an Evite event draft by providing title, start datetime, and template name. Confirms details before creating, then verifies drafts to return the event ID.

Instructions

Create an Evite event (as a draft). Requires title, start_datetime, and template_name. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Evite answers a create with a 500 even when the draft IS created; this tool handles that by re-listing your drafts, and returns created:true with the eventId, or created:"unknown" when it cannot confirm — never call it again for the same event; check the drafts instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesEvent title.
messageNoEvent message / description.
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
end_datetimeNoEnd datetime (ISO 8601, event-local).
template_nameYesInvitation template name (required by the create API; e.g. a gallery design id).
start_datetimeYesStart datetime (ISO 8601, event-local). Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Must be true to proceed. Without this, the tool returns a preview.",
-  "type": "boolean"
-}
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.5.0

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses the critical quirk that Evite returns 500 even when the draft is created, explains the tool's compensating behavior (re-listing drafts), and defines the created:true/created:"unknown" result semantics. It also exposes the two-step confirmation behavior. Annotations only say the call is not read-only and not destructive, so the description carries the full behavioral burden and satisfies it.

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 dense with dense parentheticals and a long compound final sentence, so it is not elegantly structured. However, every sentence earns its place: the confirmation protocol and the 500-error handling are both essential for correct invocation, and the core purpose is front-loaded.

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

Completeness5/5

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

For a high-complexity tool with no output schema and minimal annotations, the description covers all critical operational aspects: required inputs, confirmation mechanics in both client modes, the error-ambiguity fallback, return-value semantics, and the prohibition on retrying. An agent has everything needed to invoke it correctly.

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 names the three required parameters but that is redundant with the schema's required array; it does tie confirmToken into the confirmation workflow, yet the schema already explains confirmToken's two-step semantics in detail. The description adds modest value beyond the schema but does not meaningfully compensate beyond baseline.

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 a specific verb and resource ('Create an Evite event (as a draft)'), and the draft qualifier distinguishes it from evite_send, evite_update_event, and evite_cancel_event among siblings. An agent can immediately tell what this tool does and how it differs from related tools.

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

Usage Guidelines5/5

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

It names the three required parameters upfront, describes the confirmation flow for both client modes, and gives explicit when-not-to-use guidance: never call again for the same event when created:"unknown" — check drafts instead. This is explicit, actionable routing advice that goes well beyond a basic 'use when you need X'.

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

Deploy Server

Other Tools