Skip to main content
Glama

Reachout recovery meetings

Find online meetings

find_online_meetings
Read-onlyIdempotent

Online meetings (and hybrid ones, which can be joined online) with how to join, page by page.

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

Input Schema

NameRequiredDescriptionDefault
dayNoWeekdays: 0 = Sunday ... 6 = Saturday. Default: all.
limitNoHow many to return. Default 25.
cursorNoFor the next page: next_cursor from the previous answer.
fellowshipNoFellowship codes, e.g. ["AA", "NA", "AL-ANON", "SMART"]; see list_fellowships. Default: all.
include_hybridNoInclude hybrid meetings. Default true.
min_secular_scoreNoLowest secular score to include: 3 = secular-friendly or better, 5 = listed as secular. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/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 the safety profile is fully covered without the description. The description does add useful context about the response: each meeting includes join instructions and results are paginated. It says nothing about ordering, total counts, or what a hybrid entry looks like.

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?

It is a single short sentence with no filler, and the key concept (online + hybrid joinable online) is front-loaded. The parenthetical is slightly awkward and 'page by page' is an odd way to phrase pagination, keeping it below a 5.

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?

With six optional parameters, no required inputs, and no output schema, the description covers the identity of the results but not their shape beyond join information. For a read-only discovery tool this is adequate, though an agent still cannot tell what fields each meeting carries or how large pages can get from prose alone.

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 every one of the six parameters is already documented with defaults and ranges, making 3 the baseline. The phrase 'hybrid ones, which can be joined online' loosely reinforces the include_hybrid filter's meaning, but the description adds no real semantics for day, limit, cursor, fellowship, or min_secular_score.

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 specific resource (online meetings, including joinable hybrid ones) and a distinguishing payload ('how to join'), which separates it from location-based siblings like find_meetings_near. It lacks an explicit verb and never names an alternative, so it stops short of full sibling differentiation.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus find_meetings_near, list_meetings_in_area, or get_meeting, nor any prerequisite guidance. The only usage hint ('page by page') is about pagination, not tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources