Skip to main content
Glama

Reachout recovery meetings

List source lists

list_sources
Read-onlyIdempotent

The public meeting lists Reachout reads, with links and when each was last read. Give a country or a fellowship (or both).

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

Input Schema

NameRequiredDescriptionDefault
countryNoTwo-letter country code.
fellowshipNoFellowship codes, e.g. ["AA", "NA", "AL-ANON", "SMART"]; see list_fellowships. Default: all.

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, closed-world behavior, so the safety profile is fully covered. The description's real addition is the return shape — links plus last-read timestamps — which matters because there is no output schema. It says nothing about ordering, count limits, or what an empty result means.

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 short sentences, front-loaded with what the tool returns before the filter instruction. The phrase 'with links and when each was last read' is slightly clunky but carries real information.

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 two-optional-parameter read tool with full annotation coverage, the description supplies the one thing structured data lacks: the shape of the result. Missing only minor operational details such as result ordering or size, which are low-risk for a list endpoint.

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 both parameters are documented with formats (two-letter code, fellowship code examples). The description only adds that the filters can be combined, which is marginal value beyond the zero-required-parameters schema.

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 (the public meeting lists Reachout reads) and the fields returned (links and last-read timestamps), so an agent knows exactly what it gets. It is distinct from siblings like list_meetings_in_area or find_meetings_near, though it never explicitly says so.

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?

'Give a country or a fellowship (or both)' tells the agent how to scope the call and that either filter is optional. There is no explicit statement of when to prefer this over siblings (e.g., discovery of data sources vs. searching meetings), so usage is only implied.

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