The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
List the authenticated user's tasks. Use status to choose which set: "needs-action" (the default) for open tasks, "completed" for finished ones. One call returns one set or the other, never both — issue two calls if you need both. AI-suggested (pending/triaging) and dismissed (rejected) tasks are never returned by this tool. Filters: priority, tagId, updatedAfter. Only one of priority/tagId can be used per request. Priority order is high, medium, normal, low. "normal" (the default) sits between medium and low. Returns tasks with their titles, due dates, priority, tags, and more, most recently modified first, capped at 50 per call. If truncated is true the cap was reached and more matched: narrow with updatedAfter before counting or summarizing. Large pages may omit optional fields; those names appear in elidedFields when that happens. Connected integration tasks (Todoist, Linear, and others) are listed by list_integration_tasks.
The description explains the capability, when to use it, and what to expect.
Inputs90/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
status
Which tasks to list. "needs-action" (the default) returns open tasks; "completed" returns finished tasks instead of open ones, not alongside them. Pair "completed" with updatedAfter to find recently finished work — recency is by last-modified time, not completion time, so a task finished earlier but edited recently also matches. Say so when reporting.
Clear enough to supply this argument.
priority
Filter by priority. Priority order is high, medium, normal, low. "normal" (the default) sits between medium and low. Cannot be combined with tagId in one request.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
tagId
Filter by tag ID (returns tasks that have this tag)
Clear enough to supply this argument.
updatedAfter
ISO 8601 local date-time or calendar date; only return tasks updated after this time. Do not include Z or a timezone offset — the value is read in ianaTimeZone.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ianaTimeZone
IANA time zone (e.g. Europe/Zurich) used to interpret dates and to express returned timestamps. Defaults to the user's configured time zone.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_tasks",
"title": "List Tasks",
"description": "List the authenticated user's tasks. Use status to choose which set: \"needs-action\" (the default) for open tasks, \"completed\" for finished ones. One call returns one set or the other, never both — issue two calls if you need both. AI-suggested (pending/triaging) and dismissed (rejected) tasks are never returned by this tool. Filters: priority, tagId, updatedAfter. Only one of priority/tagId can be used per request. Priority order is high, medium, normal, low. \"normal\" (the default) sits between medium and low. Returns tasks with their titles, due dates, priority, tags, and more, most recently modified first, capped at 50 per call. If truncated is true the cap was reached and more matched: narrow with updatedAfter before counting or summarizing. Large pages may omit optional fields; those names appear in elidedFields when that happens. Connected integration tasks (Todoist, Linear, and others) are listed by list_integration_tasks.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"tagId": {
"anyOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "null"
}
],
"description": "Filter by tag ID (returns tasks that have this tag)"
},
"status": {
"anyOf": [
{
"enum": [
"needs-action",
"completed"
],
"type": "string"
},
{
"type": "null"
}
],
"description": "Which tasks to list. \"needs-action\" (the default) returns open tasks; \"completed\" returns finished tasks instead of open ones, not alongside them. Pair \"completed\" with updatedAfter to find recently finished work — recency is by last-modified time, not completion time, so a task finished earlier but edited recently also matches. Say so when reporting."
},
"priority": {
"anyOf": [
{
"enum": [
"high",
"medium",
"normal",
"low"
],
"type": "string"
},
{
"type": "null"
}
],
"description": "Filter by priority. Priority order is high, medium, normal, low. \"normal\" (the default) sits between medium and low. Cannot be combined with tagId in one request."
},
"ianaTimeZone": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"description": "IANA time zone (e.g. Europe/Zurich) every local date-time in this call is interpreted in, and that date-times in the response are rendered in. Defaults to the user's configured time zone, so set it whenever the request names a zone — asking for 09:00 UTC means sending 09:00 here with ianaTimeZone \"UTC\", not 09:00 alone."
},
{
"type": "null"
}
],
"description": "IANA time zone (e.g. Europe/Zurich) used to interpret dates and to express returned timestamps. Defaults to the user's configured time zone."
},
"updatedAfter": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"description": "ISO 8601 local date-time without timezone suffix (e.g. 2025-06-15T09:00:00) or calendar date (e.g. 2025-06-15). Do not include Z or a timezone offset — the zone comes from ianaTimeZone, which defaults to the user's configured time zone."
},
{
"type": "null"
}
],
"description": "ISO 8601 local date-time or calendar date; only return tasks updated after this time. Do not include Z or a timezone offset — the value is read in ianaTimeZone."
}
}
},
"annotations": {
"title": "List Tasks",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
Retrieve one or more tasks by their IDs. Returns an array in input order. Each entry is either a task object (type: 'task') or an error object ({ id, error }) for IDs that could not be fetched. IDs from connected integrations (Todoist, Linear, and others) are retrieved by get_integration_tasks.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
ids
Array of task IDs to retrieve (obtained from list_tasks)
Clear enough to supply this argument.
ianaTimeZone
Not provided
Missing description. Explain what this value means and how to supply it.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_tasks",
"title": "Get Tasks",
"description": "Retrieve one or more tasks by their IDs. Returns an array in input order. Each entry is either a task object (type: 'task') or an error object ({ id, error }) for IDs that could not be fetched. IDs from connected integrations (Todoist, Linear, and others) are retrieved by get_integration_tasks.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"ids"
],
"properties": {
"ids": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"minItems": 1,
"description": "Array of task IDs to retrieve (obtained from list_tasks)"
},
"ianaTimeZone": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"description": "IANA time zone (e.g. Europe/Zurich) every local date-time in this call is interpreted in, and that date-times in the response are rendered in. Defaults to the user's configured time zone, so set it whenever the request names a zone — asking for 09:00 UTC means sending 09:00 here with ianaTimeZone \"UTC\", not 09:00 alone."
},
{
"type": "null"
}
]
}
}
},
"annotations": {
"title": "Get Tasks",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description84/100
List tasks from one connected task integration such as Todoist, Linear, Google Tasks, Microsoft To Do, ClickUp, or Notion. accountId is a task-integration account from list_accounts (integrationGroup: tasks). Morgen's own task list is list_tasks. Full task details by ID are get_integration_tasks.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
2 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
accountId
Connected task-integration account ID from list_accounts with integrationGroup: tasks (Todoist, Linear, Google Tasks, and others).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Maximum tasks to fetch (1–100). The provider default is used when omitted.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ianaTimeZone
Not provided
Missing description. Explain what this value means and how to supply it.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_integration_tasks",
"title": "List Integration Tasks",
"description": "List tasks from one connected task integration such as Todoist, Linear, Google Tasks, Microsoft To Do, ClickUp, or Notion. accountId is a task-integration account from list_accounts (integrationGroup: tasks). Morgen's own task list is list_tasks. Full task details by ID are get_integration_tasks.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"accountId"
],
"properties": {
"limit": {
"anyOf": [
{
"type": "integer",
"maximum": 100,
"minimum": 1
},
{
"type": "null"
}
],
"description": "Maximum tasks to fetch (1–100). The provider default is used when omitted."
},
"accountId": {
"type": "string",
"minLength": 1,
"description": "Connected task-integration account ID from list_accounts with integrationGroup: tasks (Todoist, Linear, Google Tasks, and others)."
},
"ianaTimeZone": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"description": "IANA time zone (e.g. Europe/Zurich) every local date-time in this call is interpreted in, and that date-times in the response are rendered in. Defaults to the user's configured time zone, so set it whenever the request names a zone — asking for 09:00 UTC means sending 09:00 here with ianaTimeZone \"UTC\", not 09:00 alone."
},
{
"type": "null"
}
]
}
}
},
"annotations": {
"title": "List Integration Tasks",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Retrieve one or more tasks from one connected task integration (Todoist, Linear, and others). accountId is a task-integration account from list_accounts (integrationGroup: tasks); IDs come from list_integration_tasks for that account. Returns an array in input order. Each entry is either a task object (type: 'task') or an error object ({ id, error }). Morgen's own task list is retrieved by get_tasks.
The description explains the capability, when to use it, and what to expect.
Inputs58/100
2 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
accountId
Connected task-integration account ID the tasks belong to, from list_accounts with integrationGroup: tasks (Todoist, Linear, Google Tasks, and others).
Clear enough to supply this argument.
ids
Array of task IDs to retrieve (obtained from list_integration_tasks), at most 50
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
ianaTimeZone
Not provided
Missing description. Explain what this value means and how to supply it.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_integration_tasks",
"title": "Get Integration Tasks",
"description": "Retrieve one or more tasks from one connected task integration (Todoist, Linear, and others). accountId is a task-integration account from list_accounts (integrationGroup: tasks); IDs come from list_integration_tasks for that account. Returns an array in input order. Each entry is either a task object (type: 'task') or an error object ({ id, error }). Morgen's own task list is retrieved by get_tasks.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"accountId",
"ids"
],
"properties": {
"ids": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 50,
"minItems": 1,
"description": "Array of task IDs to retrieve (obtained from list_integration_tasks), at most 50"
},
"accountId": {
"type": "string",
"minLength": 1,
"description": "Connected task-integration account ID the tasks belong to, from list_accounts with integrationGroup: tasks (Todoist, Linear, Google Tasks, and others)."
},
"ianaTimeZone": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"description": "IANA time zone (e.g. Europe/Zurich) every local date-time in this call is interpreted in, and that date-times in the response are rendered in. Defaults to the user's configured time zone, so set it whenever the request names a zone — asking for 09:00 UTC means sending 09:00 here with ianaTimeZone \"UTC\", not 09:00 alone."
},
{
"type": "null"
}
]
}
}
},
"annotations": {
"title": "Get Integration Tasks",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description71/100
Create a new task. At minimum a title is required. Optional fields: description, due date, estimated duration, priority, tags. Priority order is high, medium, normal, low. "normal" (the default) sits between medium and low.
The description explains the capability, when to use it, and what to expect.
Inputs25/100
2 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
title
Not provided
Missing description. Explain what this value means and how to supply it.
description
Not provided
Missing description. Explain what this value means and how to supply it.
estimatedDurationMinutes
Not provided
Missing description. Explain what this value means and how to supply it.
priority
Not provided
Missing description. Explain what this value means and how to supply it.
tags
Tag IDs to assign (obtained from list_tags, or from create_tag for a new tag). Tag names are not accepted; unknown ids are rejected.
Clear enough to supply this argument.
due
Not provided
Missing description. Explain what this value means and how to supply it.
earliestStartDate
Not provided
Missing description. Explain what this value means and how to supply it.
source
URL linking to the source of this task (e.g. Slack thread, email, web page)
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description71/100
Update an existing task. Only provided fields are changed.
The description explains the capability, when to use it, and what to expect.
Inputs93/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
id
ID of the task to update (obtained from list_tasks)
Clear enough to supply this argument.
title
Updated task title. Null is ignored — titles cannot be cleared.
Clear enough to supply this argument.
description
Updated description. null is no change; clear it with clearFields.
Clear enough to supply this argument.
estimatedDurationMinutes
Estimated duration in minutes. null is no change; clear it with clearFields.
Clear enough to supply this argument.
priority
Task priority. Priority order is high, medium, normal, low. "normal" (the default) sits between medium and low. "normal" clears it to the default. null is no change.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
tags
Tag IDs (obtained from list_tags, or from create_tag for a new tag) — replaces the full tag list. null is no change; clear all tags with clearFields. Tag names are not accepted; unknown ids are rejected.
Clear enough to supply this argument.
due
Due date as YYYY-MM-DD (e.g. 2025-06-15). null is no change; clear it with clearFields.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
earliestStartDate
Earliest start date as YYYY-MM-DD (e.g. 2025-06-15). null is no change; clear it with clearFields.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
source
URL linking to the source of this task (e.g. Slack thread, email, web page). null is no change; remove it with clearFields.
Clear enough to supply this argument.
clearFields
Fields to clear: description, estimatedDurationMinutes, priority (to the default), tags (all), due, earliestStartDate, source. Do not also send a value for a cleared field.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "close_task",
"title": "Close Task",
"description": "Mark a task as completed. If the task is recurring, completing it automatically advances the task to its next occurrence.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "ID of the task to mark as completed (obtained from list_tasks)"
}
}
},
"annotations": {
"title": "Close Task",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description93/100
Reopen a previously completed task, marking the whole task as not completed. This does not target a single occurrence of a recurring task and does not undo any recurrence advance caused by a prior close — it only clears the task's completed state.
The description explains the capability, when to use it, and what to expect.
Inputs98/100
Input documentation gives an agent enough context to populate the arguments.
id
ID of the completed task to reopen (obtained from list_tasks)
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "reopen_task",
"title": "Reopen Task",
"description": "Reopen a previously completed task, marking the whole task as not completed. This does not target a single occurrence of a recurring task and does not undo any recurrence advance caused by a prior close — it only clears the task's completed state.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "ID of the completed task to reopen (obtained from list_tasks)"
}
}
},
"annotations": {
"title": "Reopen Task",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description94/100
List the tags (categories) of the authenticated user, most recently modified first, 50 per page. When nextCursor is present, calling again with cursor fetches the next page; a tag is only known to be absent once no nextCursor remains. Tag ids can be used with list_tasks to filter by tag, with create_task/update_task to assign tags, and with update_tag/delete_tag. create_tag creates a tag that does not exist yet.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
cursor
Opaque cursor from a previous list_tags response's nextCursor. Omit to start from the first page.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_tags",
"title": "List Tags",
"description": "List the tags (categories) of the authenticated user, most recently modified first, 50 per page. When nextCursor is present, calling again with cursor fetches the next page; a tag is only known to be absent once no nextCursor remains. Tag ids can be used with list_tasks to filter by tag, with create_task/update_task to assign tags, and with update_tag/delete_tag. create_tag creates a tag that does not exist yet.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"cursor": {
"anyOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "null"
}
],
"description": "Opaque cursor from a previous list_tags response's nextCursor. Omit to start from the first page."
}
}
},
"annotations": {
"title": "List Tags",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
Create a new tag (category) for the authenticated user and return it. The returned id is what create_task / update_task tags accept. Fails if a tag with the same name already exists (list_tags shows existing tags).
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
name
Tag name. Must not match an existing tag of the user (case-sensitive).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
color
Hex color in #rrggbb form (e.g. #ff8800). A random light color is assigned when omitted.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_tag",
"title": "Create Tag",
"description": "Create a new tag (category) for the authenticated user and return it. The returned id is what create_task / update_task tags accept. Fails if a tag with the same name already exists (list_tags shows existing tags).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"minLength": 1,
"description": "Tag name. Must not match an existing tag of the user (case-sensitive)."
},
"color": {
"anyOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "null"
}
],
"description": "Hex color in #rrggbb form (e.g. #ff8800). A random light color is assigned when omitted."
}
}
},
"annotations": {
"title": "Create Tag",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description97/100
List the user's calendars (name, account, access rights, sharing). By default returns calendars the user has not hidden in the client app. Set includeHidden to return all calendars, including calendars they hid or disabled. Each calendar has role (primary | contextual) and optional isHidden. Role meanings (also returned as roleExplanation): primary — Calendar whose events block availability and should be considered for scheduling decisions. contextual — Calendar used as contextual information, not as the user's own schedule. Its events can be shown/read, but they do not mean the user is busy: exclude them from availability, free/busy calculations and open-slot searches. isSharedWithMe / ownedBy mark calendars shared with the user.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
includeHidden
Include all calendars, including calendars the user has hidden or disabled in the client app. Leave this false unless you need calendars that are normally out of view. Defaults to false (visible calendars only).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_calendars",
"title": "List Calendars",
"description": "List the user's calendars (name, account, access rights, sharing). By default returns calendars the user has not hidden in the client app. Set includeHidden to return all calendars, including calendars they hid or disabled. Each calendar has role (primary | contextual) and optional isHidden. Role meanings (also returned as roleExplanation): primary — Calendar whose events block availability and should be considered for scheduling decisions. contextual — Calendar used as contextual information, not as the user's own schedule. Its events can be shown/read, but they do not mean the user is busy: exclude them from availability, free/busy calculations and open-slot searches. isSharedWithMe / ownedBy mark calendars shared with the user.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"includeHidden": {
"anyOf": [
{
"type": "boolean"
},
{
"type": "null"
}
],
"description": "Include all calendars, including calendars the user has hidden or disabled in the client app. Leave this false unless you need calendars that are normally out of view. Defaults to false (visible calendars only)."
}
}
},
"annotations": {
"title": "List Calendars",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description98/100
List calendar events within a date range. Request only the date range you need. Maximum range is 1 year. Timed event start/end are returned as wall-clock times in timeZone (or the user's configured time zone), matching the client app calendar display. All-day event end is exclusive (a one-day event starting 2026-09-15 has end 2026-09-16). Large lists may omit optional fields under token pressure; omitted names appear in elidedFields. Pass includeFields only when strictly needed. When calendars are omitted, each event has calendarRole: only primary events are the user's own schedule; contextual events are context and must not count as the user being busy. Cancelled events are omitted. Invites the account owner declined are omitted by default (includeDeclined=true includes them; they are marked isDeclined). When calendars are omitted, automatically queries the user's visible calendars across all connected accounts. When calendars are explicitly provided, only events:read scope is required. partialFailures lists what could not be read: a calendar (calendarId, plus calendarName when calendars were omitted) when only some calendars of an account failed, or the whole account otherwise.
The description explains the capability, when to use it, and what to expect.
Inputs64/100
5 of 7 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
start
Start of the query range in ISO 8601 local date-time (e.g. 2025-01-01T00:00:00). Do not include Z or a timezone offset — the range is read in timeZone.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
end
End of the range in ISO 8601 local date-time (e.g. 2025-01-31T23:59:59). Do not include Z or a timezone offset — the range is read in timeZone. Request only the date range you need. Maximum range is 1 year.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
timeZone
Not provided
Missing description. Explain what this value means and how to supply it.
calendars › anyOf › 0 › items › accountId
Calendar account ID (obtained from list_calendars)
Clear enough to supply this argument.
calendars › anyOf › 0 › items › calendarIds
Not provided
Missing description. Explain what this value means and how to supply it.
includeDeclined
Include events the account owner declined. Defaults to false (client app calendar default). Declined invites often remain status=confirmed on Google — they are not cancelled. When included, those declined events have isDeclined=true / userRSVPStatus=declined.
Clear enough to supply this argument.
includeFields
Compressible event fields to keep even when the list is large (calendarName, attendees, description, privacy, recurrence, color). description is omitted from list_events unless listed here. Use only when strictly needed for this call — each field increases response size. Requested fields may make the response exceed its normal token budget. For details on a few specific events, prefer get_events instead.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "list_events",
"title": "List Events",
"description": "List calendar events within a date range. Request only the date range you need. Maximum range is 1 year. Timed event start/end are returned as wall-clock times in timeZone (or the user's configured time zone), matching the client app calendar display. All-day event end is exclusive (a one-day event starting 2026-09-15 has end 2026-09-16). Large lists may omit optional fields under token pressure; omitted names appear in elidedFields. Pass includeFields only when strictly needed. When calendars are omitted, each event has calendarRole: only primary events are the user's own schedule; contextual events are context and must not count as the user being busy. Cancelled events are omitted. Invites the account owner declined are omitted by default (includeDeclined=true includes them; they are marked isDeclined). When calendars are omitted, automatically queries the user's visible calendars across all connected accounts. When calendars are explicitly provided, only events:read scope is required. partialFailures lists what could not be read: a calendar (calendarId, plus calendarName when calendars were omitted) when only some calendars of an account failed, or the whole account otherwise.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"start",
"end"
],
"properties": {
"end": {
"type": "string",
"minLength": 1,
"description": "End of the range in ISO 8601 local date-time (e.g. 2025-01-31T23:59:59). Do not include Z or a timezone offset — the range is read in timeZone. Request only the date range you need. Maximum range is 1 year."
},
"start": {
"type": "string",
"minLength": 1,
"description": "Start of the query range in ISO 8601 local date-time (e.g. 2025-01-01T00:00:00). Do not include Z or a timezone offset — the range is read in timeZone."
},
"timeZone": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"description": "IANA time zone (e.g. Europe/Zurich) every local date-time in this call is interpreted in, and that date-times in the response are rendered in. Defaults to the user's configured time zone, so set it whenever the request names a zone — asking for 09:00 UTC means sending 09:00 here with ianaTimeZone \"UTC\", not 09:00 alone."
},
{
"type": "null"
}
]
},
"calendars": {
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"required": [
"accountId",
"calendarIds"
],
"properties": {
"accountId": {
"type": "string",
"minLength": 1,
"description": "Calendar account ID (obtained from list_calendars)"
},
"calendarIds": {
"type": "array",
"items": {
"type": "string",
"minLength": 1,
"description": "Calendar ID from that account"
},
"minItems": 1
}
}
},
"minItems": 1
},
{
"type": "null"
}
],
"description": "Calendars to query. When omitted, automatically resolves the user's visible calendars across all accounts (requires calendars:read scope)."
},
"includeFields": {
"anyOf": [
{
"type": "array",
"items": {
"enum": [
"calendarName",
"attendees",
"description",
"privacy",
"recurrence",
"color"
],
"type": "string"
}
},
{
"type": "null"
}
],
"description": "Compressible event fields to keep even when the list is large (calendarName, attendees, description, privacy, recurrence, color). description is omitted from list_events unless listed here. Use only when strictly needed for this call — each field increases response size. Requested fields may make the response exceed its normal token budget. For details on a few specific events, prefer get_events instead."
},
"includeDeclined": {
"anyOf": [
{
"type": "boolean"
},
{
"type": "null"
}
],
"description": "Include events the account owner declined. Defaults to false (client app calendar default). Declined invites often remain status=confirmed on Google — they are not cancelled. When included, those declined events have isDeclined=true / userRSVPStatus=declined."
}
}
},
"annotations": {
"title": "List Events",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Retrieve one or more calendar events by their IDs. Timed event start/end are returned as wall-clock times in timeZone (or the user's configured time zone), matching the client app calendar display. All-day event end is exclusive (a one-day event starting 2026-09-15 has end 2026-09-16). Returns full event details for found events (including cancelled or declined ones, with isCancelled / isDeclined) and error entries for events that could not be retrieved.
The description explains the capability, when to use it, and what to expect.
Inputs50/100
1 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
ids
Array of event IDs to retrieve (obtained from list_events, or a meeting session's calendarEventId or calendarSeriesId)
Clear enough to supply this argument.
timeZone
Not provided
Missing description. Explain what this value means and how to supply it.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "get_events",
"title": "Get Events",
"description": "Retrieve one or more calendar events by their IDs. Timed event start/end are returned as wall-clock times in timeZone (or the user's configured time zone), matching the client app calendar display. All-day event end is exclusive (a one-day event starting 2026-09-15 has end 2026-09-16). Returns full event details for found events (including cancelled or declined ones, with isCancelled / isDeclined) and error entries for events that could not be retrieved.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"ids"
],
"properties": {
"ids": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"minItems": 1,
"description": "Array of event IDs to retrieve (obtained from list_events, or a meeting session's calendarEventId or calendarSeriesId)"
},
"timeZone": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"description": "IANA time zone (e.g. Europe/Zurich) every local date-time in this call is interpreted in, and that date-times in the response are rendered in. Defaults to the user's configured time zone, so set it whenever the request names a zone — asking for 09:00 UTC means sending 09:00 here with ianaTimeZone \"UTC\", not 09:00 alone."
},
{
"type": "null"
}
]
}
}
},
"annotations": {
"title": "Get Events",
"readOnlyHint": true,
"openWorldHint": false,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description87/100
Create a new calendar event. Requires account ID, calendar ID, title, start time, duration, and isAllDay. For timed events, timeZone defaults to the user's time zone when omitted or null. For all-day events, duration is a whole number of calendar days (P1D is one day, P2D is two); the exclusive end is start plus duration (a one-day event starting 2026-09-15 has end 2026-09-16). An all-day start can be a date (2026-09-15) or local midnight (2026-09-15T00:00:00). Optionally add attendees — this sends calendar invitations via the provider. By default, a video conferencing link (Google Meet or Microsoft Teams) is added based on the calendar provider.
The description explains the capability, when to use it, and what to expect.
Inputs55/100
9 of 15 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
accountId
Account ID to create the event in (obtained from list_calendars)
Clear enough to supply this argument.
title
Not provided
Missing description. Explain what this value means and how to supply it.
description
Not provided
Missing description. Explain what this value means and how to supply it.
calendarId
Calendar ID to create the event in (obtained from list_calendars)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
start
Start time in ISO 8601 local date-time format (e.g. 2025-06-15T09:00:00). Do not include Z or a timezone offset — this is the wall-clock start in timeZone, which defaults to the user's time zone. An all-day event also accepts a date (e.g. 2026-09-15), read as 2026-09-15T00:00:00.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
duration
Event duration in ISO 8601 duration format (e.g. PT1H for 1 hour, PT30M for 30 minutes, P1D for one all-day calendar day). All-day events use whole-day durations: P1D is one day, P2D is two consecutive days. The exclusive end date is start plus duration (a one-day event on 2026-09-15 has end 2026-09-16).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
timeZone
Not provided
Missing description. Explain what this value means and how to supply it.
isAllDay
Whether this is an all-day event. When true, timeZone should be null. All-day duration is counted in whole calendar days with an exclusive end (P1D covers only the start date; list_events / get_events return end as the next day).
Clear enough to supply this argument.
freeBusyStatus
Not provided
Missing description. Explain what this value means and how to supply it.
privacy
Not provided
Missing description. Explain what this value means and how to supply it.
location
Not provided
Missing description. Explain what this value means and how to supply it.
attendees › anyOf › 0 › items › email
Attendee email address
Clear enough to supply this argument.
attendees › anyOf › 0 › items › name
Attendee display name
Clear enough to supply this argument.
taskId
Link this event to a task by ID (obtained from list_tasks). Creates a scheduled time block for the task.
Clear enough to supply this argument.
addConferencingLink
Add a video conferencing link (Google Meet for Google calendars, Microsoft Teams for Outlook) to the event. Defaults to true; set to false to create an event without a conferencing link.
Clear enough to supply this argument.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "create_event",
"title": "Create Event",
"description": "Create a new calendar event. Requires account ID, calendar ID, title, start time, duration, and isAllDay. For timed events, timeZone defaults to the user's time zone when omitted or null. For all-day events, duration is a whole number of calendar days (P1D is one day, P2D is two); the exclusive end is start plus duration (a one-day event starting 2026-09-15 has end 2026-09-16). An all-day start can be a date (2026-09-15) or local midnight (2026-09-15T00:00:00). Optionally add attendees — this sends calendar invitations via the provider. By default, a video conferencing link (Google Meet or Microsoft Teams) is added based on the calendar provider.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"accountId",
"title",
"calendarId",
"start",
"duration",
"isAllDay"
],
"properties": {
"start": {
"type": "string",
"minLength": 1,
"description": "Start time in ISO 8601 local date-time format (e.g. 2025-06-15T09:00:00). Do not include Z or a timezone offset — this is the wall-clock start in timeZone, which defaults to the user's time zone. An all-day event also accepts a date (e.g. 2026-09-15), read as 2026-09-15T00:00:00."
},
"title": {
"type": "string",
"minLength": 1
},
"taskId": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"description": "Link this event to a task by ID (obtained from list_tasks). Creates a scheduled time block for the task."
},
"privacy": {
"anyOf": [
{
"enum": [
"public",
"private",
"secret"
],
"type": "string",
"description": "Event visibility: public (visible to everyone), private (details hidden), or secret (not visible)"
},
{
"type": "null"
}
]
},
"duration": {
"type": "string",
"minLength": 1,
"description": "Event duration in ISO 8601 duration format (e.g. PT1H for 1 hour, PT30M for 30 minutes, P1D for one all-day calendar day). All-day events use whole-day durations: P1D is one day, P2D is two consecutive days. The exclusive end date is start plus duration (a one-day event on 2026-09-15 has end 2026-09-16)."
},
"isAllDay": {
"type": "boolean",
"description": "Whether this is an all-day event. When true, timeZone should be null. All-day duration is counted in whole calendar days with an exclusive end (P1D covers only the start date; list_events / get_events return end as the next day)."
},
"location": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
]
},
"timeZone": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"description": "IANA time zone for start/end wall-clock times (e.g. Europe/Zurich). For timed events this is the request/user display zone — not the event's original storage zone."
},
{
"type": "null"
}
]
},
"accountId": {
"type": "string",
"minLength": 1,
"description": "Account ID to create the event in (obtained from list_calendars)"
},
"attendees": {
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"required": [
"email"
],
"properties": {
"name": {
"anyOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "null"
}
],
"description": "Attendee display name"
},
"email": {
"type": "string",
"minLength": 1,
"description": "Attendee email address"
}
}
}
},
{
"type": "null"
}
],
"description": "Event attendees. Adding attendees sends calendar invitations via the provider."
},
"calendarId": {
"type": "string",
"minLength": 1,
"description": "Calendar ID to create the event in (obtained from list_calendars)"
},
"description": {
"anyOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "null"
}
]
},
"freeBusyStatus": {
"anyOf": [
{
"enum": [
"free",
"busy"
],
"type": "string",
"description": "Whether the event blocks availability (busy) or not (free)"
},
{
"type": "null"
}
]
},
"addConferencingLink": {
"anyOf": [
{
"type": "boolean"
},
{
"type": "null"
}
],
"description": "Add a video conferencing link (Google Meet for Google calendars, Microsoft Teams for Outlook) to the event. Defaults to true; set to false to create an event without a conferencing link."
}
}
},
"annotations": {
"title": "Create Event",
"readOnlyHint": false,
"openWorldHint": true,
"destructiveHint": false
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description78/100
Update an existing calendar event. Only provided fields are changed. Timing updates interpret start as display wall-clock times in timing.timeZone, or the user's time zone when timing.timeZone is null; the event's original storage timezone is preserved. For all-day events, timing.duration is a whole number of calendar days (P1D is one day, P2D is two). list_events and get_events return an exclusive all-day end: a one-day event starting 2026-09-15 has end 2026-09-16, matching duration P1D. An all-day timing.start can be a date (2026-09-15) or local midnight (2026-09-15T00:00:00).
The description explains the capability, when to use it, and what to expect.
Inputs87/100
16 of 17 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
id
ID of the event to update (obtained from list_events)
Clear enough to supply this argument.
accountId
Account ID that owns the event (obtained from list_calendars)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
calendarId
Calendar ID that contains the event (obtained from list_calendars)
Clear enough to supply this argument.
title
Not provided
Missing description. Explain what this value means and how to supply it.
timing › anyOf › 0 › start
Updated start as wall-clock local date-time (e.g. 2025-06-15T09:00:00). Do not include Z or a timezone offset — this is the display wall-clock in timing.timeZone (defaults to the user's time zone). The event's storage timezone is preserved server-side. When timing.isAllDay is true, a date (e.g. 2026-09-15) is also accepted, read as 2026-09-15T00:00:00.
Clear enough to supply this argument.
timing › anyOf › 0 › duration
Updated duration in ISO 8601 duration format (e.g. PT1H for 1 hour, P1D for one all-day calendar day). All-day events use whole-day durations: P1D is one day, P2D is two consecutive days. The exclusive end date is start plus duration (a one-day event on 2026-09-15 has end 2026-09-16).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
timing › anyOf › 0 › timeZone
Display IANA time zone for interpreting start (e.g. Europe/Zurich). Send null to use the user's time zone. Does not change the event's storage timezone.
Clear enough to supply this argument.
timing › anyOf › 0 › isAllDay
Whether this is an all-day event. All-day duration is counted in whole calendar days with an exclusive end (P1D covers only the start date; list_events / get_events return end as the next day).
Clear enough to supply this argument.
description
Updated event description in plain text or HTML. null is no change; clear it with clearFields.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
freeBusyStatus
Whether the event blocks availability (busy) or not (free). null is no change; reset it with clearFields.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
privacy
Event visibility: public, private, or secret. null is no change; reset it with clearFields.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
location
Event location name. null is no change; clear it with clearFields.
Clear enough to supply this argument.
clearFields
Fields to clear: description, location, or freeBusyStatus and privacy (to the default). Do not also send a value for a cleared field.
Clear enough to supply this argument.
attendees › anyOf › 0 › items › email
Attendee email address
Clear enough to supply this argument.
attendees › anyOf › 0 › items › remove
true removes this attendee. null or false adds or keeps them.
Clear enough to supply this argument.
clearAttendees
true removes every attendee from the event, which cancels their invitations. null or false leaves the attendee list unchanged. Cannot be combined with a non-empty attendees list — pass one or the other.
Clear enough to supply this argument.
seriesUpdateMode
Scope of update for recurring events: single (this occurrence only), all (entire series), or future (this and all future occurrences)
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared
Original tool metadata
{
"name": "update_event",
"title": "Update Event",
"description": "Update an existing calendar event. Only provided fields are changed. Timing updates interpret start as display wall-clock times in timing.timeZone, or the user's time zone when timing.timeZone is null; the event's original storage timezone is preserved. For all-day events, timing.duration is a whole number of calendar days (P1D is one day, P2D is two). list_events and get_events return an exclusive all-day end: a one-day event starting 2026-09-15 has end 2026-09-16, matching duration P1D. An all-day timing.start can be a date (2026-09-15) or local midnight (2026-09-15T00:00:00).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id",
"accountId",
"calendarId"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "ID of the event to update (obtained from list_events)"
},
"title": {
"anyOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "null"
}
]
},
"timing": {
"anyOf": [
{
"type": "object",
"required": [
"start",
"duration",
"isAllDay"
],
"properties": {
"start": {
"type": "string",
"minLength": 1,
"description": "Updated start as wall-clock local date-time (e.g. 2025-06-15T09:00:00). Do not include Z or a timezone offset — this is the display wall-clock in timing.timeZone (defaults to the user's time zone). The event's storage timezone is preserved server-side. When timing.isAllDay is true, a date (e.g. 2026-09-15) is also accepted, read as 2026-09-15T00:00:00."
},
"duration": {
"type": "string",
"minLength": 1,
"description": "Updated duration in ISO 8601 duration format (e.g. PT1H for 1 hour, P1D for one all-day calendar day). All-day events use whole-day durations: P1D is one day, P2D is two consecutive days. The exclusive end date is start plus duration (a one-day event on 2026-09-15 has end 2026-09-16)."
},
"isAllDay": {
"type": "boolean",
"description": "Whether this is an all-day event. All-day duration is counted in whole calendar days with an exclusive end (P1D covers only the start date; list_events / get_events return end as the next day)."
},
"timeZone": {
"anyOf": [
{
"type": "string",
"minLength": 1,
"description": "IANA time zone for start/end wall-clock times (e.g. Europe/Zurich). For timed events this is the request/user display zone — not the event's original storage zone."
},
{
"type": "null"
}
],
"description": "Display IANA time zone for interpreting start (e.g. Europe/Zurich). Send null to use the user's time zone. Does not change the event's storage timezone."
}
}
},
{
"type": "null"
}
],
"description": "Timing update — provide all fields together or omit entirely."
},
"privacy": {
"anyOf": [
{
"enum": [
"public",
"private",
"secret"
],
"type": "string",
"description": "Event visibility: public (visible to everyone), private (details hidden), or secret (not visible)"
},
{
"type": "null"
}
],
"description": "Event visibility: public, private, or secret. null is no change; reset it with clearFields."
},
"location": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"description": "Event location name. null is no change; clear it with clearFields."
},
"accountId": {
"type": "string",
"minLength": 1,
"description": "Account ID that owns the event (obtained from list_calendars)"
},
"attendees": {
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"required": [
"email"
],
"properties": {
"email": {
"type": "string",
"minLength": 1,
"description": "Attendee email address"
},
"remove": {
"anyOf": [
{
"type": "boolean"
},
{
"type": "null"
}
],
"description": "true removes this attendee. null or false adds or keeps them."
}
}
}
},
{
"type": "null"
}
],
"description": "Merge-patch attendees. Listed attendees are merged with the existing ones; attendees that are not listed are preserved. Adding an attendee sends a calendar invitation. Set \"remove\" to true to drop one attendee, or use clearAttendees to drop all of them. null or [] changes nothing. Attendee names cannot be changed — providers resolve display names from their directories."
},
"calendarId": {
"type": "string",
"minLength": 1,
"description": "Calendar ID that contains the event (obtained from list_calendars)"
},
"clearFields": {
"anyOf": [
{
"type": "array",
"items": {
"enum": [
"description",
"location",
"freeBusyStatus",
"privacy"
],
"type": "string"
}
},
{
"type": "null"
}
],
"description": "Fields to clear: description, location, or freeBusyStatus and privacy (to the default). Do not also send a value for a cleared field."
},
"description": {
"anyOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "null"
}
],
"description": "Updated event description in plain text or HTML. null is no change; clear it with clearFields."
},
"clearAttendees": {
"anyOf": [
{
"type": "boolean"
},
{
"type": "null"
}
],
"description": "true removes every attendee from the event, which cancels their invitations. null or false leaves the attendee list unchanged. Cannot be combined with a non-empty attendees list — pass one or the other."
},
"freeBusyStatus": {
"anyOf": [
{
"enum": [
"free",
"busy"
],
"type": "string",
"description": "Whether the event blocks availability (busy) or not (free)"
},
{
"type": "null"
}
],
"description": "Whether the event blocks availability (busy) or not (free). null is no change; reset it with clearFields."
},
"seriesUpdateMode": {
"anyOf": [
{
"enum": [
"single",
"all",
"future"
],
"type": "string"
},
{
"type": "null"
}
],
"description": "Scope of update for recurring events: single (this occurrence only), all (entire series), or future (this and all future occurrences)"
}
}
},
"annotations": {
"title": "Update Event",
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": true
}
}
The title clearly communicates the tool’s action and subject. Keep it concise.
Description96/100
List connected calendar, task, and video accounts, optionally filtered by integration type. Task integration account IDs (Todoist, Linear, Google Tasks, and others) are used with list_integration_tasks. Returns account ID, integration provider, capabilities, display name, and email addresses.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
integrationGroup
Filter accounts by integration type (e.g. 'calendars' for calendar accounts only)
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description95/100
Search Google Maps for places matching a query. Returns place suggestions with display text (description, suitable as an event location name) and a Google placeId for commute calculations with compute_commute_time.
The description explains the capability, when to use it, and what to expect.
Inputs75/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
query
Free-text place query (address, venue name, city, etc.).
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
limit
Maximum number of suggestions to return (1–10). Defaults to 5.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations75/100
Declare idempotentHint based on the tool’s actual behavior.
The title clearly communicates the tool’s action and subject. Keep it concise.
Description86/100
Compute travel time and distance between two places using Google Directions (driving, walking, transit, or cycling). Supports leave-at / arrive-by timing and returns transit line details when available.
The description explains the capability, when to use it, and what to expect.
Inputs95/100
Remove repeated schema validation from descriptions; focus on meaning and usage context.
origin
Start location: address, place name, latitude,longitude, or a Google place ID written as placeId:<placeId> (the placeId values search_locations returns).
Clear enough to supply this argument.
destination
End location: same formats as origin, including placeId:<placeId> from search_locations.
Clear enough to supply this argument.
mode
Travel mode. Defaults to driving.
Clear enough to supply this argument.
waypoints
Intermediate stops, pipe-separated per Google Directions (addresses or placeId:<placeId> values), or include optimize:true to reorder. Driving/walking/bicycling only.
morgen setup, tools, quality score, publishing readiness, and alternatives.
How do I add morgen to Claude, ChatGPT, or Cursor?
Add morgen to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://mcp.morgen.so/mcp.
Is morgen MCP ready for ChatGPT and Claude?
As of November 19, 2026, morgen scores 100/100 on Manufact's MCP publishing checklist. The scan meets ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.
How clear is morgen's MCP tool documentation?
As of November 19, 2026, morgen scores 79/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 22 of 22 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.
What are the best alternatives to morgen?
As of November 20, 2026, alternatives to morgen in productivity on the Manufact MCP leaderboard include AdaptlyPost, Notion MCP, Paperpal, Skyward, and VantagePeers.
How can morgen improve its MCP documentation?
create_task is the lowest-scoring reviewed tool at 60/100. No output schema is declared. Add one for structured results so clients can interpret returned fields. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.
Not your MCP?
Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.