Skip to main content
Glama

Reachout recovery meetings

Code for a web page of meetings

website_code
Read-onlyIdempotent

Ready-to-paste HTML and JavaScript for a web page that shows meetings near a place, loaded live from the Reachout API (so it stays current), grouped by day, each linked to its source list, with the Reachout credit badge. Use this when someone wants meetings on their website.

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

Input Schema

NameRequiredDescriptionDefault
headingNoOptional heading for the list, e.g. "Meetings near Duluth".
latitudeYes
longitudeYes
fellowshipNoFellowship codes, e.g. ["AA", "NA", "AL-ANON", "SMART"]; see list_fellowships. Default: all.
radius_milesNoDefault 25.
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 readOnly, idempotent, non-destructive, so the safety profile is covered. The description does add real behavioral value by describing the generated artifact — live API loading so the page stays current, day grouping, source links, mandatory credit badge. It omits whether any API key or account setup is required for the generated page to work, which is the main behavioral gap.

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?

Two sentences, front-loaded with the artifact type and its properties, then the usage trigger. Dense but every clause carries information; a slight cost is that the first sentence is long and stacks several feature clauses.

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 6-parameter generator with no output schema, the description does the important work of explaining what the returned code looks like and what it includes. Remaining gaps are minor: it does not state the return container (single code string) or any prerequisites for the generated page to function.

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 67%, and the description adds no parameter-level meaning: latitude/longitude are only implied by 'near a place', and heading, fellowship, radius_miles, and min_secular_score are described only in the schema. The schema does the heavy lifting here, so 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?

The description names the concrete artifact (ready-to-paste HTML and JavaScript for a meetings web page) and its key characteristics (live from the Reachout API, grouped by day, linked to source lists, credit badge). This makes it clearly distinct from data-returning siblings like find_meetings_near or list_meetings_in_area, though it never explicitly says 'this returns code, not meeting data'.

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?

It gives a clear trigger: 'Use this when someone wants meetings on their website.' That reliably separates it from search/list tools. It stops short of explicit exclusions (e.g. 'use find_meetings_near if you just need the data in-chat'), so it is clear context without full routing guidance.

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