Skip to main content
Glama
Sign In

OTP

by io.github.david-steel
OverviewDiscussionsAdmin

List meetings

list_meetings
Read-only

List Delta Meetings for the authenticated organization, newest first, as summary rows: id, title, when, type, status, team, and whether a transcript and a summary exist. Filter by meeting_type or status; with neither, every type is returned. To find the NEXT meeting, pass upcoming=true: only meetings scheduled from now on, soonest first (newest-first plus a limit would otherwise show the furthest-out recurring instances and miss this week's). This tool deliberately does NOT return transcripts or notes -- call get_meeting_transcript or get_meeting_agenda with an id from here for the contents of one meeting.

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. Defaults to 25.
statusNo
upcomingNoOnly meetings scheduled from now on, soonest first. Use this to find the next meeting.
meeting_typeNoe.g. 'leadership', 'departmental', '1on1'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already establish that this is a read-only, non-destructive operation, and the description adds substantial behavioral detail beyond them: newest-first ordering, summary-row fields, filter defaults, the upcoming ordering caveat, and the deliberate exclusion of transcripts and notes. The explanation of why upcoming=true matters when using a limit is particularly useful for correct invocation.

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?

The description is front-loaded with the core behavior and then moves through filtering, upcoming semantics, and exclusions in a logical order. The parenthetical about newest-first plus a limit is slightly long but earns its place by preventing a likely misuse.

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?

Although there is no output schema, the description enumerates the summary fields returned, covers filtering and ordering semantics, explains the upcoming edge case, and routes the agent to the correct sibling tools for meeting contents. Nothing essential for correct selection or invocation 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?

Schema coverage is 75%, and the description adds real meaning for meeting_type, status, and upcoming, including the important default that omitting both filters returns every type. It does not add much beyond the schema for limit, but the schema itself documents that parameter adequately.

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 uses a specific verb and resource ('List Delta Meetings') and immediately defines the scope: authenticated organization, newest first, summary rows only. It distinguishes itself from meeting-content siblings by explicitly saying transcripts and notes are not returned and naming get_meeting_transcript and get_meeting_agenda instead.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit usage guidance: filter by meeting_type or status, omit both to return every type, and pass upcoming=true specifically to find the next meeting. It also states the alternative for meeting contents, so an agent knows when to switch to get_meeting_transcript or get_meeting_agenda.

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

All OTP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources