Skip to main content
Glama

List meetings

list_meetings
Read-onlyIdempotent

List meetings from a chosen date range, newest first, with titles, dates, participants, and main summary points. Use it to review recent calls or find your last conversation with someone.

Instructions

Meetings in a period, newest first: title, date, participants and the main point of the summary. For questions like "What calls did I have this week?", "Catch me up on yesterday's meetings", "When did I last talk to Daniel?" Read-only.

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_meetings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many meetings to return, newest first
sinceNoDate YYYY-MM-DD, inclusive; empty — no bound
untilNoDate YYYY-MM-DD, inclusive; empty — no bound

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so "Read-only." adds nothing. The description does contribute behavior the annotations cannot: results are ordered newest-first and each item carries a summary gist rather than full content, which tells the agent this is a lightweight listing.

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?

The opening clause is front-loaded with the resource, ordering and return shape, and the example queries are compact and directly actionable. Slightly list-like phrasing, but no sentence is filler.

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?

With an output schema present, return-value explanation is not required, yet the description still summarizes the payload shape usefully. For a three-optional-parameter listing tool this covers what an agent needs; the only real gap is how this differs from the search sibling when answering people-centric questions.

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%, with limit, since and until each documented including YYYY-MM-DD format and inclusive bounds, so the baseline is 3. The description only loosely gestures at the parameters via "in a period" and "newest first" and adds no syntax or default guidance beyond the schema.

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 names a concrete resource and scope ("Meetings in a period, newest first") and enumerates the returned fields (title, date, participants, main point of summary), so an agent knows this is a cardinality-many listing rather than a single-record fetch. It does not explicitly contrast itself with siblings like get_meeting or search, leaving the boundary between list_meetings and search to be inferred.

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?

Three sample user questions ("What calls did I have this week?", "Catch me up on yesterday's meetings", "When did I last talk to Daniel?") give concrete trigger context, which is stronger than a generic "use for listing". However, no exclusions or alternatives are stated, and one example ("When did I last talk to Daniel?") plausibly overlaps with the search sibling, with no rule to disambiguate.

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

Deploy Server

Other Tools