meetergo MCP server

Official

by meetergo

Overview Schema Source Related Servers Score Discussions Admin

TypeScript

Local

List appointments

list_appointments

Read-onlyIdempotent

Retrieve scheduled appointments with pagination and filters, including status and appointmentId for subsequent updates or cancellations.

Instructions

Return appointments with pagination and filters, including the appointmentId needed for changes. Every item carries a confirmed or cancelled status; cancelled items are not upcoming appointments. Pages are 0-indexed.

Input Schema

TableJSON Schema

Name	Required	Description
`end`	No	ISO 8601 timestamp. Only appointments starting at or before this.
`page`	No	0-indexed page number. Defaults to 0.
`start`	No	Only appointments starting at or after this
`search`	No	Free-text search
`sortBy`	No
`status`	No
`pageSize`	No
`meetingTypeId`	No
`sortDirection`	No

Output Schema

TableJSON Schema

Name	Required	Description
`page`	No	0-indexed page
`total`	No	Total matches
`pageSize`	No	Page size
`appointments`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed12 schema fields changedv0.6.25Aug 28, 2026

addedInput schema / properties / end

Added value: +{
+  "description": "ISO 8601 timestamp. Only appointments starting at or before this.",
+  "type": "string"
+}

removedInput schema / properties / limit

Removed value: -{
-  "maximum": 100,
-  "minimum": 1,
-  "type": "integer"
-}

addedInput schema / properties / meetingTypeId
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / page / description

Added value: +"0-indexed page number. Defaults to 0."

changedInput schema / properties / page / minimum
```
Previous value: -1New value: +0
```

addedInput schema / properties / pageSize

Added value: +{
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / search

Added value: +{
+  "description": "Free-text search",
+  "type": "string"
+}

addedInput schema / properties / sortBy

Added value: +{
+  "enum": [
+    "appointment.start",
+    "appointment.createdAt"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sortDirection

Added value: +{
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "type": "string"
+}

addedInput schema / properties / start

Added value: +{
+  "description": "Only appointments starting at or after this",
+  "type": "string"
+}

addedInput schema / properties / status
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "One page of appointments",
+  "properties": {
+    "appointments": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "description": "An appointment with its derived status",
+            "properties": {
+              "attendees": {
+                "anyOf": [
+                  {
+                    "items": {
+                      "additionalProperties": true,
+                      "description": "A person on an appointment",
+                      "properties": {
+                        "email": {
+                          "$ref": "#/properties/appointments/anyOf/0/items/properties/id"
+                        },
+                        "firstname": {
+                          "$ref": "#/properties/appointments/anyOf/0/items/properties/id"
+                        },
+                        "fullname": {
+                          "$ref": "#/properties/appointments/anyOf/0/items/properties/id"
+                        },
+                        "id": {
+                          "$ref": "#/properties/appointments/anyOf/0/items/properties/id",
+                          "description": "The attendeeId other tools take"
+                        },
+                        "lastname": {
+                          "$ref": "#/properties/appointments/anyOf/0/items/properties/id"
+                        },
+                        "phone": {
+                          "$ref": "#/properties/appointments/anyOf/0/items/properties/id"
+                        },
+                        "timezone": {
+                          "$ref": "#/properties/appointments/anyOf/0/items/properties/id"
+                        }
+                      },
+                      "type": "object"
+                    },
+                    "type": "array"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "end": {
+                "$ref": "#/properties/appointments/anyOf/0/items/properties/id",
+                "description": "End, ISO 8601"
+              },
+              "hosts": {
+                "anyOf": [
+                  {
+                    "items": {
+                      "additionalProperties": true,
+                      "properties": {},
+                      "type": "object"
+                    },
+                    "type": "array"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "id": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "isCancelled": {
+                "$ref": "#/properties/appointments/anyOf/0/items/properties/rescheduled"
+              },
+              "location": {
+                "description": "Where the meeting happens, as configured on the meeting type"
+              },
+              "meetingTypeId": {
+                "$ref": "#/properties/appointments/anyOf/0/items/properties/id"
+              },
+              "notes": {
+                "description": "Host-side note and booking-form answers"
+              },
+              "rescheduled": {
+                "description": "Present and true when the appointment was moved at least once",
+                "type": [
+                  "boolean",
+                  "null"
+                ]
+              },
+              "start": {
+                "$ref": "#/properties/appointments/anyOf/0/items/properties/id",
+                "description": "Start, ISO 8601"
+              },
+              "status": {
+                "anyOf": [
+                  {
+                    "enum": [
+                      "confirmed",
+                      "cancelled"
+                    ],
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "Derived by this server: never report a cancelled appointment as upcoming"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "page": {
+      "description": "0-indexed page"
+    },
+    "pageSize": {
+      "description": "Page size"
+    },
+    "total": {
+      "description": "Total matches"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.1Jul 29, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable behavioral context beyond those annotations: pages are 0-indexed, every item carries a confirmed/cancelled status, and cancelled items are excluded from upcoming appointments. This helps an agent interpret pagination and status semantics correctly.

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?

Three focused sentences, each carrying meaningful information: the core purpose, the status behavior, and the pagination indexing. There is no redundancy or filler, and the most important fact (appointmentId for changes) appears early.

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

Completeness3/5

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

The description covers core list behavior and pagination, but with nine optional parameters and low schema coverage, it leaves several parameters uninterpreted. The presence of an output schema and annotations lessens the burden, but the lack of guidance about filter semantics and when to choose this tool over siblings keeps it from being complete.

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 only 44%, so the description should compensate by explaining the less-documented parameters. It does not: meetingTypeId, sortBy, sortDirection, and pageSize are not mentioned at all, and status is only touched on in a general semantic sense. The only useful parameter-level additions are the 0-indexed page note and the status filtering implication, which is insufficient for nine parameters.

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 operation: returning appointments with pagination and filtering, and highlights the appointmentId as the needed identifier for later changes. It does not explicitly distinguish itself from sibling list tools like get_todays_appointments, so it misses the final point of differentiation, but the verb+resource+scope are specific.

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?

There is no explicit guidance on when to use this tool versus alternatives such as get_todays_appointments or get_appointment. The note about cancelled items not being upcoming appointments implies a filtering use case, but it never names alternatives or exclusion conditions, leaving the agent to infer when to select this tool.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/meetergo/meetergo-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server