Skip to main content
Glama

Reachout recovery meetings

Find meetings near a place

find_meetings_near
Read-onlyIdempotent

In-person and hybrid recovery meetings near a point, nearest first, with distance. Use the place's latitude and longitude.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "find_meetings_near"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoWeekdays: 0 = Sunday ... 6 = Saturday. Default: all.
limitNoHow many to return. Default 25.
latitudeYes
longitudeYes
radius_kmNoSearch radius in kilometres, instead of radius_miles.
attendanceNoDefault: both.
fellowshipNoFellowship codes, e.g. ["AA", "NA", "AL-ANON", "SMART"]; see list_fellowships. Default: all.
radius_milesNoSearch radius in miles. Default 25. (Or radius_km.)
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.6/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 non-open-world, so the safety profile is covered. The description usefully adds that results are sorted nearest-first and include a distance value, but says nothing about result count limits, pagination, or what happens when no meetings fall in radius.

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?

Two short sentences with zero waste: scope and ordering come first, then the input guidance. Nothing is repeated from the schema or annotations.

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 a 9-parameter, read-only search tool with no output schema, the definition covers what is returned (meetings with distance, sorted) and how to supply the required coordinates; the remaining parameter semantics live in a well-populated schema. A reference to a sibling for online meetings is the main omission.

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 coverage is 78%, so most parameters (day, limit, radius, attendance, fellowship, min_secular_score) are already documented inline. The description adds only the coordinate-usage hint and does not clarify units/format for latitude and longitude, the two schema-undocumented parameters, nor how radius_km and radius_miles interact.

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 and scope: 'In-person and hybrid recovery meetings near a point', which implicitly separates it from the online-meeting sibling, and adds ordering semantics ('nearest first, with distance'). It stops short of explicitly naming an alternative for online-only searches, but the resource and modality are unambiguous.

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?

'Use the place's latitude and longitude' tells the agent which inputs to supply, and the attendance constraint ('in-person and hybrid') implies when this tool applies. There is no explicit when-not guidance and no named alternative (e.g. find_online_meetings) for the complementary case.

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