GetSign MCP

getsign_get_signer_data

Read-onlyIdempotent

Signers who must sign, plus copy-only recipients, as two labeled lists.

    - signers: people whose signature is required (emails, roles, isCompleted).
    - copy_recipients: people who only receive a copy after everyone finishes —
      they do not sign. The emails arg on getsign_send_signature_request is
      copy-only, never a signer.
    - isSigningOrderRequired / signing_order: whether later signers wait until
      the previous person signs. Read-only here. Set it with
      getsign_save_document_configuration action=signing_order (do not open
      the PDF editor just for order).

    Pass envelope_id + item_id for both lists. Pass envelope_id alone for
    copy recipients only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`item_id`	No
`envelope_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: the emails arg on getsign_send_signature_request is copy-only and never a signer, and signing order is read-only here. This clarifies data semantics beyond what annotations provide.

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 description is well-structured with bullet points and front-loads the core purpose. Each sentence earns its place, though the signing-order note is slightly tangential to the tool's primary function. Still, it's compact and scannable.

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 read-only tool with no output schema, the description covers the key inputs, the two output categories, and the relationship to sibling tools. It doesn't describe the exact return format, but the labeled lists are named and explained. The main gap is not specifying what happens if both parameters are omitted, but the usage guidance is otherwise 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 description coverage is 0%, so the description carries the full burden. It explains that envelope_id and item_id are both needed for signers, but envelope_id alone suffices for copy recipients. This adds real meaning beyond the bare schema, though it doesn't describe the exact format of the IDs or the return structure.

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 clearly states the tool returns signers and copy-only recipients as two labeled lists, with explicit definitions of each. It distinguishes itself from related tools by naming getsign_send_signature_request and getsign_save_document_configuration, making its purpose unambiguous.

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?

The description provides explicit usage guidance: pass envelope_id + item_id for both lists, or envelope_id alone for copy recipients only. It also tells the agent when NOT to use this tool (do not open the PDF editor for signing order) and directs to getsign_save_document_configuration instead, which is strong alternative routing.

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

All GetSign MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?