Skip to main content
Glama

Aisle

by wedding.aisle
OverviewDiscussionsAdmin

List My Wedding Events

list_my_events
Read-onlyIdempotent

Lists the selected wedding's events in date order with their dates, times, venues, dress codes and descriptions. Optional filters narrow results by event type or by a range of calendar days in the wedding's time zone; the total counts the events returned. Each event names the other events whose times overlap it. Requires sign-in.

Input Schema

NameRequiredDescriptionDefault
toNoLast day to include, as YYYY-MM-DD in the wedding's time zone.
fromNoFirst day to include, as YYYY-MM-DD in the wedding's time zone.
typeNoFilter by event type, one type or a list such as ["ceremony", "reception"].
wedding_idNoIdentifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
+  "description": "First day to include, as YYYY-MM-DD in the wedding's time zone.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / to
      Added value: +{
+  "description": "Last day to include, as YYYY-MM-DD in the wedding's time zone.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "welcome_dinner",
+        "ceremony",
+        "reception",
+        "brunch",
+        "rehearsal",
+        "cocktail_hour",
+        "after_party",
+        "activity",
+        "other"
+      ],
+      "type": "string"
+    },
+    {
+      "items": {
+        "enum": [
+          "welcome_dinner",
+          "ceremony",
+          "reception",
+          "brunch",
+          "rehearsal",
+          "cocktail_hour",
+          "after_party",
+          "activity",
+          "other"
+        ],
+        "type": "string"
+      },
+      "minItems": 1,
+      "type": "array"
+    }
+  ],
+  "description": "Filter by event type, one type or a list such as [\"ceremony\", \"reception\"]."
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds real context beyond that: the sign-in requirement, date ordering, that the total reflects returned events, and that each event names its time-overlapping peers.

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?

Three front-loaded sentences with no filler; the core purpose and output shape come first, with filters and auth note following. Slightly dense but every sentence carries information.

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?

With no output schema, the description compensates by enumerating returned attributes (dates, times, venues, dress codes, descriptions, overlap names, total count) and the auth prerequisite. An agent has enough to call and interpret results 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 both filters and wedding_id are fully documented by the schema, setting the baseline at 3. The description restates the filter dimensions and the wedding's time zone but adds no syntax beyond what the schema already provides.

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?

States a specific verb (Lists) and resource (wedding's events) plus the ordering and returned fields. This clearly separates it from list_my_guests, list_my_accommodations, and the singular get_my_event sibling.

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?

Explains that optional filters narrow results by event type or day range, and that sign-in is required, giving clear usage context. It never explicitly contrasts with get_my_event (single event) or add/update/remove_my_event, so the when-not-alternatives guidance is absent.

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

All Aisle toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources