ClearPolicy

List Signing Requests Tool

list-signing-requests-tool

Read-onlyIdempotent

Check who has signed a document and who hasn't. Filter by document, person, or status (pending, signed, expired, etc.) to track compliance.

Input Schema

TableJSON Schema

Name	Required	Description
`status`	No	Filter by status: pending (open), signed (completed), or an exact status (created, sent, viewed, attested, expired, canceled, bounced, failed, complained, suppressed).
`person_id`	No	Filter by person ULID.
`document_id`	No	Filter by document ULID.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`requests`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 2, 2026

changedInput schema / properties / status / description

Previous value: -"Filter by status: created, sent, viewed, attested, expired, or canceled."New value: +"Filter by status: pending (open), signed (completed), or an exact status (created, sent, viewed, attested, expired, canceled, bounced, failed, complained, suppressed)."

changedInput schema / properties / status / enum

Previous value: -[
-  "created",
-  "sent",
-  "viewed",
-  "attested",
-  "expired",
-  "canceled",
-  "bounced",
-  "failed",
-  "complained",
-  "suppressed"
-]New value: +[
+  "pending",
+  "signed",
+  "created",
+  "sent",
+  "viewed",
+  "attested",
+  "expired",
+  "canceled",
+  "bounced",
+  "failed",
+  "complained",
+  "suppressed"
+]

Changed1 schema field changedSep 10, 2026
- changedOutput schema / properties / requests / items / properties / attestation_type / enum
```
Previous value: -[
-  "acknowledgment",
-  "signature"
-]New value: +[
+  "signature",
+  "acknowledgment"
+]
```
Changed4 schema fields changedJul 17, 2026
- addedOutput schema / properties / requests / items / properties / document / properties / app_url
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / requests / items / properties / document / required
```
Previous value: -[
-  "id",
-  "name",
-  "resource_uri"
-]New value: +[
+  "id",
+  "name",
+  "resource_uri",
+  "app_url"
+]
```
- addedOutput schema / properties / requests / items / properties / person / properties / app_url
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / requests / items / properties / person / required
```
Previous value: -[
-  "id",
-  "name",
-  "email",
-  "resource_uri"
-]New value: +[
+  "id",
+  "name",
+  "email",
+  "resource_uri",
+  "app_url"
+]
```

Changed2 schema fields changedJul 2, 2026

changedInput schema / properties / status / enum

Previous value: -[
-  "created",
-  "sent",
-  "viewed",
-  "attested",
-  "expired",
-  "canceled",
-  "bounced",
-  "failed",
-  "complained"
-]New value: +[
+  "created",
+  "sent",
+  "viewed",
+  "attested",
+  "expired",
+  "canceled",
+  "bounced",
+  "failed",
+  "complained",
+  "suppressed"
+]

changedOutput schema / properties / requests / items / properties / status / enum

Previous value: -[
-  "created",
-  "sent",
-  "viewed",
-  "attested",
-  "expired",
-  "canceled",
-  "bounced",
-  "failed",
-  "complained"
-]New value: +[
+  "created",
+  "sent",
+  "viewed",
+  "attested",
+  "expired",
+  "canceled",
+  "bounced",
+  "failed",
+  "complained",
+  "suppressed"
+]

Changed1 schema field changedJul 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "requests": {
+      "items": {
+        "properties": {
+          "attestation_type": {
+            "enum": [
+              "acknowledgment",
+              "signature"
+            ],
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "attested_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "document": {
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "resource_uri": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "name",
+              "resource_uri"
+            ],
+            "type": "object"
+          },
+          "expired_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "person": {
+            "properties": {
+              "email": {
+                "type": "string"
+              },
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "resource_uri": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "name",
+              "email",
+              "resource_uri"
+            ],
+            "type": "object"
+          },
+          "resource_uri": {
+            "type": "string"
+          },
+          "sent_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "enum": [
+              "created",
+              "sent",
+              "viewed",
+              "attested",
+              "expired",
+              "canceled",
+              "bounced",
+              "failed",
+              "complained"
+            ],
+            "type": "string"
+          },
+          "viewed_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "status",
+          "resource_uri"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "requests"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJun 21, 2026

changedInput schema / properties / status / enum

Previous value: -[
-  "created",
-  "sent",
-  "viewed",
-  "attested",
-  "expired",
-  "canceled"
-]New value: +[
+  "created",
+  "sent",
+  "viewed",
+  "attested",
+  "expired",
+  "canceled",
+  "bounced",
+  "failed",
+  "complained"
+]

First observedMar 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the compliance-tracking framing and glosses status semantics ('pending', 'signed', 'expired'), which is modest added context, but it says nothing about result volume, pagination, or ordering.

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?

Two short sentences, front-loaded with the core purpose followed by the filtering capability. No filler or repetition, though the status examples are redundant with the schema enum.

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 simple, read-only, zero-required-parameter list tool with a full-coverage schema and an output schema, the description covers purpose and filtering adequately. Only pagination/ordering behavior is unaddressed, and the output schema presumably handles the return shape.

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 100% and the description only restates the filter dimensions and a partial list of statuses already enumerated in the schema enum. Baseline 3 applies since the schema carries the parameter semantics.

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 clear verb+resource ('Check who has signed a document and who hasn't') and frames the tool as a listing/tracking query over signing requests. It is distinguishable from singular siblings like get-signing-request-tool, but it never explicitly names that sibling or the document/person list tools, so differentiation is left to inference.

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?

'Filter by document, person, or status ... to track compliance' implies the usage context (compliance auditing) but gives no explicit when-to-use/when-not or alternative tool routing. There is no guidance pointing to get-signing-request-tool for a single record versus this list tool.

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

All ClearPolicy 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?