Skip to main content
Glama
FluidMeet MCP Server

FluidMeet MCP Server

by dl6nm

Meet List

meet_list
Read-onlyIdempotent

List recorded meetings newest first as JSON to find a meeting ID for viewing details or summaries; optionally filter by limit or date range.

Instructions

List recorded meetings, newest first, as JSON (id, startedAt, durationSeconds, speakers, title, saved summaries). CALL THIS FIRST to find a meeting's id before using meet_show / meet_summary. An id prefix (first 8 chars) is enough elsewhere.

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": "meet_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of meetings (positive integer).
sinceNoOnly meetings since then: '7d', '24h' or 'YYYY-MM-DD'.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description still adds useful context: deterministic newest-first ordering and the exact fields returned. It stops short of describing default page size or what happens when limit is omitted, which would have completed the behavioral picture.

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?

Three short sentences, front-loaded with the action and scope, then the workflow rule, then the id-prefix tip. Nothing is redundant or buried.

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?

For a zero-required-parameter read-only list tool with full schema coverage and an output schema, everything an agent needs to call it correctly is present; listing the returned fields is mildly redundant with the output schema but doubles as a preview of what the id is used for.

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 parameters (limit, since) are already documented with a format hint for since, setting the baseline at 3. The description itself adds no parameter-level detail beyond ordering, so it neither compensates for nor degrades what the schema 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 and resource ("List recorded meetings") plus ordering ("newest first") and the return shape (JSON with id, startedAt, durationSeconds, speakers, title, saved summaries). That is enough for an agent to distinguish it from meet_show and meet_summary without opening a schema.

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?

"CALL THIS FIRST to find a meeting's id before using meet_show / meet_summary" gives an explicit ordering rule and names the alternatives it gates. The follow-up note that an 8-character id prefix suffices elsewhere removes a likely follow-up question about how to reuse the returned id.

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