Skip to main content
Glama

Docflare

Get a recipient

get_recipient
Read-only

Shows one person saved in the current Docflare workspace: their details, how many documents they signed, have still to open or sign, or declined, and those documents newest first, 10 a page, each with its document id and where it stands for them. Use it for questions such as whether someone signed a document or what is still waiting on them. The id comes from list_recipients.

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": {
      "id": "<id>"
    },
    "name": "get_recipient"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe recipient id, as returned by list_recipients.
pageNoThe page of their documents, 1 when left out.
searchNoOnly their documents whose name contains this, such as "NDA".
statusNoOnly their documents where they stand at this: waiting for their turn in a signing order, pending (not opened yet), viewed (opened, not signed), signed or declined.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the description does not need to restate safety. It adds return behavior beyond the annotations: document counts by state, newest-first ordering, 10-per-page pagination, and per-document id plus status. It does not explain error cases, but that is a minor gap for a read operation.

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?

The purpose is front-loaded, and every sentence contributes useful information about the return content and usage. The first sentence is somewhat run-on ("their details, how many documents they signed, have still to open or sign, or declined"), but it is not padded with filler.

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?

With no output schema, the description must explain the return shape, and it does: recipient details, per-status document counts, and a paginated newest-first document list with ids and statuses. It could say more about what recipient "details" include, but it is largely complete for this tool's complexity.

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 id, page, search, and status in detail. The description restates that the id comes from list_recipients and mentions 10 results per page, but adds little semantic detail beyond the schema for page, search, or status.

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 names a specific verb and resource: it "Shows one person saved in the current Docflare workspace" along with their document activity. It clearly contrasts with the plural sibling list_recipients by specifying a single recipient and pointing to list_recipients as the id source.

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 concrete when-to-use examples: "whether someone signed a document or what is still waiting on them," and says where the required id comes from. It does not state explicit exclusions, but the intended use case is clear enough to select this tool over alternatives.

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