clickedu-mcp

list_message_recipients

Lists teachers, admins, and contacts from the message compose directory, with optional name filtering. Use the result to find a recipient_id before sending a message.

Instructions

List message recipients from the compose directory (teachers, admin, contacts). Optional query filters by name substring. Use to find a recipient_id for send_message. Read-only.

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

Input Schema

Name	Required	Description	Default
`query`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose that the operation is read-only and that the filter is optional. It does not mention result size, pagination, ordering, or whether the directory is complete, which are relevant traits for a lookup tool feeding another call.

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?

Three short sentences, front-loaded with the resource and source, then the parameter behavior, then the intended use. Nothing is redundant and no sentence could be removed without losing 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 one-parameter lookup tool with an output schema and a stated read-only nature, the description covers what it returns conceptually (recipients), how to narrow it, and why the caller wants it. Minor gaps around result volume and relationship to get_chat_contacts keep it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the single 'query' parameter has no schema description at all, so the description must compensate. It does so by explaining that the parameter is optional and filters by name substring, which is the key semantic an agent needs to avoid passing a full name or ID incorrectly.

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?

States a specific verb and resource (list message recipients) plus the source directory and the recipient categories it covers (teachers, admin, contacts). It is clear on its own, though it does not explicitly distinguish itself from the overlapping sibling get_chat_contacts, leaving the agent to infer which contact list is which.

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?

The sentence 'Use to find a recipient_id for send_message' gives an explicit downstream purpose and names the consuming tool, which is genuinely useful routing information. It stops short of stating when not to use it or how it relates to the other contact-listing siblings, so no exclusions are provided.

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