Skip to main content
Glama

Docflare

Find recipients

list_recipients
Read-only

Finds the people saved in the current Docflare workspace: everyone a document went to and everyone added on its Recipients page, newest first, 10 a page. When the user names someone without giving an email, search for them here before asking for one: a single match is that person, so use their email; with several, ask which one; with none, which may be a typo, search again with one word or part of one, such as "Koch", and ask for the email only when that finds nobody either. Every word of the search must match their name, email or company, so a full name, a first name or a company all work. The answer gives total, page and more, which is true while further pages remain.

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

Input Schema

NameRequiredDescriptionDefault
pageNoThe page of the list, 1 when left out.
searchNoA name, email or company, such as "Ray Kocha" or "acme".
statusNoactive when left out; archived lists the people archived on the Recipients page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description adds ordering (newest first), page size (10), matching semantics ('every word of the search must match') and the shape of the response ('total, page and more'). It does not discuss what happens at the last page beyond 'more' being false, but the behavioral picture is otherwise rich for a safe read.

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?

Front-loaded with the core statement of what is listed, then the search fallback ladder, then the response shape. It is dense and every sentence carries information, though the long chain of conditional clauses in the middle sentence makes it slightly hard to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description names the returned fields (total, page, more) and explains their meaning, and it covers pagination defaults and search behavior. Nothing needed to call this three-parameter read tool correctly appears to be missing.

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 100%, so the baseline is 3, but the description goes beyond the schema's examples by explaining that every word must match name, email or company and that partial single-word searches are the fallback strategy. It also clarifies that 'archived' means people archived on the Recipients page rather than archived documents.

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?

States a specific verb and resource ('Finds the people saved in the current Docflare workspace') plus scope, ordering ('newest first') and page size ('10 a page'). It is clearly a listing tool over the whole workspace, distinguishable from the single-record sibling get_recipient without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit decision procedure: search here before asking for an email, treat a single match as the person, ask which one when several match, and retry with a shorter term like "Koch" when nothing matches. It even states when to finally ask for the email, which is exactly the when-to-use/when-not guidance an agent needs.

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