Skip to main content
Glama

Reachout recovery meetings

List meetings in a country or state

list_meetings_in_area
Read-onlyIdempotent

All active meetings in one country, or one state or province, page by page (follow next_cursor for more).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "list_meetings_in_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoWeekdays: 0 = Sunday ... 6 = Saturday. Default: all.
limitNoHow many to return. Default 100.
cursorNoFor the next page: next_cursor from the previous answer.
regionNoState or province code within the country: MN, ON, ... Default: the whole country.
countryYesTwo-letter country code: US, CA, GB, DE, ...
attendanceNoDefault: all.
fellowshipNoFellowship codes, e.g. ["AA", "NA", "AL-ANON", "SMART"]; see list_fellowships. Default: all.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered without the description. The description does add two useful behavioral facts beyond that: results are limited to 'active' meetings, and results are paginated via next_cursor. It does not say what happens when region is invalid or how large result sets behave.

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?

A single well-formed sentence with the scope front-loaded and the pagination instruction trailing. No filler, though the parenthetical about next_cursor duplicates what the cursor parameter already says and could be dropped.

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?

For an 8-parameter read-only listing tool with full schema coverage and no output schema, the description covers scope, the active-only filter, and pagination. It could note the default page size or hint at what a meeting record contains, since no output schema exists to carry that.

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 8 parameters is already documented with formats, ranges, and defaults. The description only echoes the cursor pagination already described in the schema, adding no new filter or format meaning; baseline 3 applies.

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?

States a specific verb+resource ('All active meetings') and a clear scope ('one country, or one state or province'), which implicitly separates it from proximity-based siblings like find_meetings_near. It stops short of naming any sibling explicitly, so an agent must infer the country/state vs. near-me dichotomy.

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

Usage Guidelines3/5

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

Usage is implied by the geographic scope (browse listings by country/region) and the pagination hint, but there is no explicit when-to-use or when-not-to-use guidance relative to find_meetings_near or find_online_meetings. An agent that wants meetings in a place would likely infer this correctly, but nothing confirms the choice.

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