Deferno MCP Server

create_event

Schedule a time-bound event with a required start time and optional end time, recurrence, labels, and subtask templates to manage deadlines and recurring tasks.

Instructions

Create a time-bound event.

complete_by is the start time (ISO-8601). end_time (if provided) must be at or after complete_by.

v0.2 optional fields:

subtask_template: list of subtask shapes materialized per occurrence.

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>",
      "complete_by": "<complete_by>"
    },
    "name": "create_event"
  }
}

Input Schema

Name	Required	Description	Default
`title`	Yes
`complete_by`	Yes
`end_time`	No
`description`	No
`labels`	No
`parent_id`	No
`recurrence`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 11, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral transparency. It discloses that complete_by is the start time and end_time must be at or after, but it does not describe return value, side effects, permission requirements, or other behavioral traits. The mention of 'subtask_template' not in the schema may mislead.

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 relatively short and front-loaded with the main purpose. However, it includes version history ('v0.2 optional fields') and a reference to a field not in the schema, which adds unnecessary noise. It could be more succinct.

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?

Given the tool has 7 parameters, no annotations, and an output schema (unseen), the description is incomplete. It does not explain what the event creation entails, what the return value is, or how events differ from tasks. Key context like prerequisites or typical usage scenarios is missing.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It explains semantics for 'complete_by' and 'end_time' but provides no information for other five parameters (title, description, labels, parent_id, recurrence). Additionally, it mentions a 'subtask_template' field that does not appear in the schema, which could cause confusion.

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 clearly states the tool creates a time-bound event, using a specific verb and resource. It clarifies that 'complete_by' is the start time. However, it does not explicitly differentiate from sibling tools like create_task or create_habit, though the term 'event' provides some distinction.

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

Usage Guidelines3/5

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

The description provides a validation rule (end_time must be after complete_by) and mentions version-specific optional fields, but it does not give explicit guidance on when to use this tool over alternatives. The context of creating an event vs. a task or habit is implied but not elaborated.

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

Deploy Server