Assinafy

Review a signature request

assinafy_review_signature_request

Read-onlyIdempotent

Preview an assinafy_create_assignment call without sending anything: same arguments, checked against the document and signers. Use it when the user wants to review before sending. Apps-capable hosts render a card whose Send button performs the request; other clients get the summary as text, and the request is sent only after the user confirms.

Input Schema

Name	Required	Description	Default
`method`	Yes		virtual
`entries`	No	Required for `collect`: field placements per page.
`message`	No	Text included in the invitation email.
`signers`	Yes
`expires_at`	No	ISO 8601; default is no expiration. Must be at least one hour in the future.
`document_id`	Yes	Document ID.
`copy_receivers`	No	Signer IDs that only receive a copy.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedInput schema / properties / signers / items / properties / verification_method / description

Previous value: -"How the signer's identity is verified before signing. `Email` (default) sends a one-time code to the signer's email; `Whatsapp` sends the code over WhatsApp — the verification itself is not billed, but it requires the WhatsApp notification channel, so the signer costs 0.45 credits (available only on paid subscriptions); `DigitalCertificate` has the signer sign with their own ICP-Brasil certificate (A1/A3) — it requires the Digital Certificate feature, the signer must have a CPF or CNPJ in `government_id`, must be alone in its signing step, and is charged 0.5 credits per signer. A CPF requires that person's certificate (an e-CPF, or an e-CNPJ naming them as legal representative); a CNPJ requires an e-CNPJ for that company, from any of its representatives. `IdDocumentFaceMatchBasic` verifies the signer from a photo of their government ID, a photo of them holding it and a liveness check — it requires the ID Document + Face Match feature, the signer must have a valid CPF in `government_id`, and is charged a per-signer fee. Omit to default to `Email`."New value: +"How the signer's identity is verified before signing. `Email` (default) sends a one-time code to the signer's email; `Whatsapp` sends the code over WhatsApp — the verification itself is not billed, but it requires the WhatsApp notification channel, so the signer costs 0.45 credits (available only on paid subscriptions); `DigitalCertificate` has the signer sign with their own ICP-Brasil certificate (A1/A3) — it requires `method: virtual`, the Digital Certificate feature, a CPF or CNPJ in `government_id`, must be alone in its signing step, and is charged 0.5 credits per signer. A CPF requires that person's certificate (an e-CPF, or an e-CNPJ naming them as legal representative); a CNPJ requires an e-CNPJ for that company, from any of its representatives. `IdDocumentFaceMatchBasic` verifies the signer from a photo of their government ID, a photo of them holding it and a liveness check — it requires the ID Document + Face Match feature, the signer must have a valid CPF in `government_id`, and is charged a per-signer fee. Omit to default to `Email`."

Changed10 schema fields changedOct 16, 2026

changedInput schema / allOf

Previous value: -[
-  {
-    "if": {
-      "properties": {
-        "method": {
-          "const": "collect"
-        }
-      },
-      "required": [
-        "method"
-      ]
-    },
-    "then": {
-      "properties": {
-        "entries": {
-          "minItems": 1
-        }
-      },
-      "required": [
-        "entries"
-      ]
-    }
-  }
-]New value: +[
+  {
+    "if": {
+      "properties": {
+        "method": {
+          "const": "collect"
+        }
+      },
+      "required": [
+        "method"
+      ]
+    },
+    "then": {
+      "properties": {
+        "entries": {
+          "minItems": 1
+        }
+      },
+      "required": [
+        "entries"
+      ]
+    }
+  },
+  {
+    "else": {
+      "properties": {
+        "signers": {
+          "items": {
+            "required": [
+              "id"
+            ]
+          }
+        }
+      }
+    },
+    "if": {
+      "properties": {
+        "estimate_only": {
+          "const": true
+        }
+      },
+      "required": [
+        "estimate_only"
+      ]
+    }
+  }
+]

changedInput schema / properties / expires_at / description

Previous value: -"ISO 8601; default is no expiration."New value: +"ISO 8601; default is no expiration. Must be at least one hour in the future."

changedInput schema / properties / signers / items / properties / notification_methods / description

Previous value: -"Channels used to notify the signer of the request. Any combination of `Email` and `Whatsapp` (WhatsApp incurs an additional cost and is available only on paid subscriptions). Omit to default to `{\"Email\"}`."New value: +"How the signer is told a signature is being requested. **Exactly one method per signer** — the array shape is historical, and sending two returns `400`. The method must also be compatible with `verification_method`: `Email` verification takes `Email`, `Whatsapp` verification takes `Whatsapp`, and `DigitalCertificate` and `IdDocumentFaceMatchBasic` take either. WhatsApp incurs an additional cost and is available only on paid subscriptions. Omit it to have it inferred from `verification_method`, or `{\"Email\"}` when neither is sent. See **Verification & Notification Methods** for the full pairing table."

addedInput schema / properties / signers / items / properties / notification_methods / example
```
Added value: +[
+  "Email"
+]
```
addedInput schema / properties / signers / items / properties / notification_methods / maxItems
```
Added value: +1
```
addedInput schema / properties / signers / items / properties / step / minimum
```
Added value: +1
```

changedInput schema / properties / signers / items / properties / verification_method / description

Previous value: -"How the signer's identity is verified before signing. `Email` (default) sends a one-time code to the signer's email; `Whatsapp` sends the code over WhatsApp — the verification itself is not billed, but it requires the WhatsApp notification channel, so the signer costs 0.45 credits (available only on paid subscriptions); `DigitalCertificate` has the signer sign with their own ICP-Brasil certificate (A1/A3) — it requires the Digital Certificate feature, the signer's CPF or CNPJ must already be registered on their Assinafy contact (added in Assinafy, never through this tool), must be alone in its signing step, and is charged 2 credits per signer. A CPF requires that person's certificate (an e-CPF, or an e-CNPJ naming them as legal representative); a CNPJ requires an e-CNPJ for that company, from any of its representatives. Omit to default to `Email`."New value: +"How the signer's identity is verified before signing. `Email` (default) sends a one-time code to the signer's email; `Whatsapp` sends the code over WhatsApp — the verification itself is not billed, but it requires the WhatsApp notification channel, so the signer costs 0.45 credits (available only on paid subscriptions); `DigitalCertificate` has the signer sign with their own ICP-Brasil certificate (A1/A3) — it requires the Digital Certificate feature, the signer must have a CPF or CNPJ in `government_id`, must be alone in its signing step, and is charged 0.5 credits per signer. A CPF requires that person's certificate (an e-CPF, or an e-CNPJ naming them as legal representative); a CNPJ requires an e-CNPJ for that company, from any of its representatives. `IdDocumentFaceMatchBasic` verifies the signer from a photo of their government ID, a photo of them holding it and a liveness check — it requires the ID Document + Face Match feature, the signer must have a valid CPF in `government_id`, and is charged a per-signer fee. Omit to default to `Email`."

changedInput schema / properties / signers / items / properties / verification_method / enum

Previous value: -[
-  "Email",
-  "Whatsapp",
-  "DigitalCertificate"
-]New value: +[
+  "Email",
+  "Whatsapp",
+  "DigitalCertificate",
+  "IdDocumentFaceMatchBasic"
+]

addedInput schema / properties / signers / items / properties / verification_method / example
```
Added value: +"Email"
```
removedInput schema / properties / signers / items / required
```
Removed value: -[
-  "id"
-]
```

Changed1 schema field changedOct 13, 2026

changedInput schema / properties / signers / items / properties / verification_method / description

Previous value: -"How the signer's identity is verified before signing. `Email` (default) sends a one-time code to the signer's email; `Whatsapp` sends the code over WhatsApp — the verification itself is not billed, but it requires the WhatsApp notification channel, so the signer costs 0.45 credits (available only on paid subscriptions); `DigitalCertificate` has the signer sign with their own ICP-Brasil certificate (A1/A3) — it requires the Digital Certificate feature, the signer must have a CPF or CNPJ in `government_id`, must be alone in its signing step, and is charged 2 credits per signer. A CPF requires that person's certificate (an e-CPF, or an e-CNPJ naming them as legal representative); a CNPJ requires an e-CNPJ for that company, from any of its representatives. Omit to default to `Email`."New value: +"How the signer's identity is verified before signing. `Email` (default) sends a one-time code to the signer's email; `Whatsapp` sends the code over WhatsApp — the verification itself is not billed, but it requires the WhatsApp notification channel, so the signer costs 0.45 credits (available only on paid subscriptions); `DigitalCertificate` has the signer sign with their own ICP-Brasil certificate (A1/A3) — it requires the Digital Certificate feature, the signer's CPF or CNPJ must already be registered on their Assinafy contact (added in Assinafy, never through this tool), must be alone in its signing step, and is charged 2 credits per signer. A CPF requires that person's certificate (an e-CPF, or an e-CNPJ naming them as legal representative); a CNPJ requires an e-CNPJ for that company, from any of its representatives. Omit to default to `Email`."

AddedOct 8, 2026

TDQS

A4.1/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, but the description adds the critical nuance that nothing is sent until the user confirms, and that the send path depends on the host (card Send button vs. text summary). That clarifies a deferred side effect the annotations alone would leave ambiguous.

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?

Three front-loaded sentences: what it does, when to use it, then host-dependent behavior. No filler, though the host-rendering sentence is the longest and could be trimmed slightly without losing meaning.

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 does address the return path ('other clients get the summary as text'), which is the minimum needed. It stops short of describing what the summary contains or what validation failures look like, which is a minor gap for a 7-parameter preview tool.

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 description coverage is 71% and the parameters are heavily documented in-schema (verification_method, notification_methods, display_settings all carry long descriptions). The description only says 'same arguments', adding no parameter-level meaning beyond what the schema provides, so baseline 3 is appropriate.

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 ('Preview an assinafy_create_assignment call without sending anything') and explicitly names the sibling it mirrors, so an agent can distinguish it from assinafy_create_assignment immediately. The added clause 'checked against the document and signers' clarifies what the preview validates.

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?

Gives a clear selection condition ('Use it when the user wants to review before sending') and implicitly routes to the alternative — the real create_assignment — when review is not wanted. It does not spell out an explicit when-not clause, but the surrounding context makes the split unambiguous.

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

All Assinafy 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.

Review a signature request

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources