Skip to main content
Glama

Find message recipients

bb_find_recipients
Read-only

Search a course's participants to get the user IDs required for sending messages. Filter by name or username within a specified course.

Instructions

Search the participants of a course so you can obtain the user ids needed by bb_send_message.

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": {
      "courseId": "<courseId>"
    },
    "name": "bb_find_recipients"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoMatch on given/family name or username
courseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results are participants with user ids, but says nothing about what happens when 'query' is omitted (does it list all participants?), result caps, or matching breadth. Useful context, but the search-scope behavior is still undisclosed.

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?

One sentence, front-loaded with the verb and resource, and closed with the concrete reason to call it. Nothing is redundant or buried.

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-parameter read-only lookup with no output schema, the description covers the purpose, the workflow dependency, and the key return value (user ids). It falls short only on unspecified behavior when 'query' is absent and on the shape/limits of the result set, which are minor for a tool this simple.

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 50%: 'query' is documented in the schema while 'courseId' has no description. The phrase 'participants of a course' weakly implies courseId scopes the search, but the description adds no format or semantics for courseId and does not explain the effect of leaving 'query' empty, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Search the participants of a course') and frames the tool's role as the id-lookup step that feeds bb_send_message. That explicit pairing lets an agent distinguish it from the other messaging tools without opening any schema.

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 states the triggering context clearly: call this when you need user ids before invoking bb_send_message. There are no exclusions or when-not conditions, and no mention of how to handle a course where the participant is not found, but the primary usage path is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.