Skip to main content
Glama

Find a group nearby

find_group_nearby
Read-only

Use this when the user wants to meditate with other people: a live group session or venue near them, or asks to start a group in their area. Not for medical questions, emergencies or a crisis. Not for general chat about meditation. Not for exact addresses: a suburb, postcode or city is enough.

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_group_nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoSuburb, postcode or city. Coarse on purpose; never an exact address.
languageNoAudio language as a BCP-47 code (en, es, pt-BR, fr, it, ja, hi, ko, hu, or any other such as pl). Always pass the language the user writes in. If the language is not available the answer says so and gives the closest live one. hi, ko and hu are beta.
radius_kmNoSearch radius in kilometres. Default 10.

Output Schema

NameRequiredDescriptionDefault
endedNo
needsNo
placeNo
statusNo
venuesNo
help_linesNo
live_groupsNo
start_a_groupNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds a real behavioral constraint the annotations do not: location input is deliberately coarse and an exact address is unnecessary, which tells the agent how to handle a user offering a street address. It says nothing about result volume, fallback behavior, or latency, and the output schema carries the return shape.

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?

Four short sentences, front-loaded with the positive trigger before the exclusions, with zero filler. Every sentence carries either the use case or a boundary condition an agent could act on.

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?

The tool has no required parameters, an output schema, and full annotation coverage, so most of the burden is already carried elsewhere. The description supplies intent, exclusions, and location granularity guidance, which is sufficient to invoke it correctly. Only a note on what to do when nothing is found nearby would make it fully self-contained.

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 100%, so the schema already documents place, language and radius_km in detail, including the language fallback and beta codes. The description adds only a reinforcement of the coarse-place constraint ('a suburb, postcode or city is enough'), which the schema property description already states. Marginal added meaning over structured data, so baseline 3 is correct.

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 states a concrete intent: find a live group meditation session or venue near the user, or help start a group in their area. That is a specific verb-plus-resource and it is clearly distinct from the other find_* tools by targeting groups/venues rather than individual sessions. It stops short of naming a sibling such as join_live_group, so the boundary with it is inferred rather than declared.

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 an explicit trigger (user wants to meditate with others, or asks to start a group) plus three concrete exclusions: medical questions, emergencies/crisis, and general meditation chat. That is strong when/when-not guidance. It never routes the agent to an alternative tool for those excluded cases, so the 'alternatives' leg of the rubric is missing.

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