Skip to main content
Glama
Sign In
PDFGate MCP Server

PDFGate MCP Server

Official
by pdfgate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_recipient

Retrieve a stored recipient by ID to check signature status and details such as pending, active, or revoked state, enrollment, and usage.

Instructions

Retrieve a stored recipient by ID. Once a stored signature was requested the response carries a signature object (status pending, active or revoked, plus requestedAt, adoptionMethod, enrolledAt, revokedAt, lastUsedAt and useCount); while the signature is active it also includes image, the signature as a PNG data URL, which can be very long.

Input Schema

NameRequiredDescriptionDefault
recipientIdYesThe recipient ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations exist, so the description shoulders the full burden, and it delivers the most important behavioral detail: the response may include a signature object with status values and timestamps, and the image field is a potentially very long PNG data URL. It omits not-found/error behavior and authentication requirements, which keeps it below a 5.

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 response shape is front-loaded in the first sentence and the caveat about the oversized image field comes last where it matters. The field enumeration is dense but each item is informative, so it does not read as 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 steps in to explain the return shape, which is the main complexity for a getter of this kind. An agent has enough to call it and interpret the response, with only error paths left unstated.

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% with one required parameter, so the schema already documents it fully. The description adds no format or sourcing hints for recipientId, matching the baseline expectation when the schema does the work.

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 states a specific verb and resource: retrieve a stored recipient by ID. The phrase 'by ID' distinguishes it from list_recipients and create_recipient, though it never names the sibling tools directly.

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?

The usage is implied by 'retrieve ... by ID' – single-recipient lookup – but does not state prerequisites, when to use it versus list_recipients, or what happens when the ID is unknown.

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

Deploy Server

Other Tools