Skip to main content
Glama
meetergo

meetergo MCP server

Official
by meetergo
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

Get today's appointments

get_todays_appointments
Read-onlyIdempotent

Retrieve today's appointments for the authenticated user. Get a precise, cost-efficient list without filtering by date.

Instructions

Return today's appointments for the authenticated user. This specialised query is cheaper and more precise than a general date-filtered appointment list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNo
appointmentsNo

Schema Changelog

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

  1. Changed1 schema field changedv0.6.25
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "Today's appointments, each with a derived status",
+  "properties": {
+    "appointments": {
+      "anyOf": [
+        {
+          "items": {
+            "$ref": "#/properties/items/anyOf/0/items"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "items": {
+      "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/items/anyOf/0/items/properties/id"
+                        },
+                        "firstname": {
+                          "$ref": "#/properties/items/anyOf/0/items/properties/id"
+                        },
+                        "fullname": {
+                          "$ref": "#/properties/items/anyOf/0/items/properties/id"
+                        },
+                        "id": {
+                          "$ref": "#/properties/items/anyOf/0/items/properties/id",
+                          "description": "The attendeeId other tools take"
+                        },
+                        "lastname": {
+                          "$ref": "#/properties/items/anyOf/0/items/properties/id"
+                        },
+                        "phone": {
+                          "$ref": "#/properties/items/anyOf/0/items/properties/id"
+                        },
+                        "timezone": {
+                          "$ref": "#/properties/items/anyOf/0/items/properties/id"
+                        }
+                      },
+                      "type": "object"
+                    },
+                    "type": "array"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "end": {
+                "$ref": "#/properties/items/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/items/anyOf/0/items/properties/rescheduled"
+              },
+              "location": {
+                "description": "Where the meeting happens, as configured on the meeting type"
+              },
+              "meetingTypeId": {
+                "$ref": "#/properties/items/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/items/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"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}
  2. First observedv0.1.1

TDQS

A4.3/5.0
Behavior3/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 useful context about the authenticated-user scope and cost/precision trade-offs, but does not describe return shape or any additional behavioral traits. This is consistent with the calibration example for covered tools.

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, no filler. The core action is front-loaded, and the differentiating rationale is provided in the second sentence. Every word earns its place.

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 zero-parameter read-only query with an output schema and strong annotations, the description is complete. It specifies the user scope, the time range, and the advantage over the alternative. Nothing an agent needs to invoke it correctly is missing.

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?

The tool has zero parameters, so the description does not need to elaborate on parameter meaning. Baseline for 0 parameters is 4; the description appropriately says nothing about parameters.

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: 'Return today's appointments for the authenticated user.' It also distinguishes itself from a general date-filtered appointment list by emphasizing it is cheaper and more precise, which clearly separates it from siblings like list_appointments.

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 description gives clear contextual guidance: use this when you need today's appointments for the authenticated user and want a cheaper, more precise query than the general date-filtered list. It implies the alternative without explicitly naming list_appointments or stating when not to use the general list, so it stops just short of full explicitness.

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

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