Skip to main content
Glama

list_events

Read-only

List all wedding events—ceremony, reception, rehearsal dinner—with RSVP counts; use full or brief views to review attendance at a glance.

Instructions

List all wedding events (ceremony, reception, rehearsal dinner, etc.) with RSVP counts

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNo"full" (default) returns the usual JSON; "brief" returns one line per item: title — <ISO date or "no date"> — <status>. Status is the RSVP counts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.1
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "\"full\" (default) returns the usual JSON; \"brief\" returns one line per item: title — <ISO date or \"no date\"> — <status>. Status is the RSVP counts.",
      +  "enum": [
      +    "full",
      +    "brief"
      +  ],
      +  "type": "string"
      +}
  2. First observedv1.4.2

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that RSVP counts are returned, which is useful, but it says nothing about ordering, pagination, empty-state behavior, or that a compact view is available.

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?

A single front-loaded sentence with zero filler. The parenthetical examples earn their place by defining what counts as an event, and the trailing clause flags the payload's key data point.

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

Completeness4/5

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

This is a simple read-only list tool with one optional, fully documented parameter and no output schema, so the description does not need to explain return values. The only minor gap is not signposting the brief view mode, which an agent could otherwise use to avoid verbose output.

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%, and the schema fully explains the view enum including the brief one-line format. The description does not reference the view option at all, so it adds no parameter meaning beyond the schema — the baseline 3 applies.

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?

States a specific verb (List) and resource (wedding events), and grounds the resource with concrete examples (ceremony, reception, rehearsal dinner) plus the included data (RSVP counts). That is enough to distinguish it from mutation siblings like update_event and set_event_guests, though no sibling is named explicitly.

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?

Usage is only implied by the verb 'List' — a reader infers this is the read path for retrieving events, with update_event as the obvious counterpart. There is no explicit when-to-use or when-not-to-use guidance and no mention of prerequisites.

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