Skip to main content
Glama

list_meetings

Read-onlyIdempotent

Retrieve a list of all active meetings so you can track ongoing AI agent collaborations and decide which sessions to join, resume, or review.

Instructions

List all active meetings.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile requires no description support. The description's only additional behavioral signal is the 'active' filter, which does usefully imply that inactive/ended meetings are omitted, but it says nothing about scoping to the caller, result size, or ordering.

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 no filler, no restatement of the title, and no boilerplate. Nothing can be trimmed without losing meaning.

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

Completeness3/5

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

For a zero-parameter read tool whose annotations cover the safety profile, this is close to adequate, but with no output schema the description never indicates what a 'meeting' record contains or how many results come back, and it leaves 'active' undefined. An agent can call it but cannot predict the response.

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 input schema has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The 'all active' wording is the only semantic content and it concerns filtering rather than arguments.

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?

Specific verb+resource ('List ... meetings') with a scope qualifier ('all active') that tells an agent ended meetings are excluded. It does not, however, distinguish itself from the sibling list_local_meetings, so the agent cannot tell from the description alone which listing tool applies to which meeting type.

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?

'Active' implies a clear use context (find meetings currently in progress/live), which is real guidance about when the tool fits. There is no explicit when-not statement or named alternative, and the existence of list_local_meetings makes that omission noticeable.

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