ClearPolicy

Get Person Tool

get-person-tool

Read-onlyIdempotent

Get a person's profile and see which documents they have or haven't signed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`person_id`	Yes	The ULID of the person.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`email`	Yes
`phone`	No
`app_url`	Yes
`archived`	Yes
`last_name`	Yes
`first_name`	No
`resource_uri`	Yes
`document_counts`	No
`groups_resource_uri`	Yes
`documents_resource_uri`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 10, 2026

addedOutput schema / properties / first_name

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / last_name
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "id",
-  "name",
-  "email",
-  "archived",
-  "resource_uri",
-  "app_url",
-  "documents_resource_uri",
-  "groups_resource_uri"
-]New value: +[
+  "id",
+  "last_name",
+  "name",
+  "email",
+  "archived",
+  "resource_uri",
+  "app_url",
+  "documents_resource_uri",
+  "groups_resource_uri"
+]

Changed5 schema fields changedJul 17, 2026

addedOutput schema / properties / app_url
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / documents_resource_uri
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / groups_resource_uri
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / resource_uri
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "id",
-  "name",
-  "email",
-  "archived"
-]New value: +[
+  "id",
+  "name",
+  "email",
+  "archived",
+  "resource_uri",
+  "app_url",
+  "documents_resource_uri",
+  "groups_resource_uri"
+]

Changed1 schema field changedJul 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "archived": {
+      "type": "boolean"
+    },
+    "document_counts": {
+      "properties": {
+        "attested_latest": {
+          "type": "integer"
+        },
+        "attested_outdated": {
+          "type": "integer"
+        },
+        "pending_attested": {
+          "type": "integer"
+        },
+        "renewal_due": {
+          "type": "integer"
+        },
+        "total": {
+          "type": "integer"
+        },
+        "unrequested": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "email": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "phone": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "email",
+    "archived"
+  ],
+  "type": "object"
+}

First observedMar 29, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds that it shows which documents are signed or not, which is useful outcome context, but does not go beyond that. Given annotations cover the core behavior, this is adequate but not extensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no redundant words. It is front-loaded with the core action and then adds the outcome detail, making it highly efficient and easy to scan.

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 one-parameter tool with an output schema and safety annotations, the description is sufficient. It states what it does and what information is returned. It could explicitly mention when to use it over list-people-tool, but the lack is minor given the clarity of purpose. Overall, it is complete for an agent to call correctly.

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 describes person_id as 'The ULID of the person.' The description itself does not add additional parameter context, so it relies fully on the schema. This is the baseline 3 since the schema does the heavy lifting.

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 verb 'Get' and resource 'person's profile', and specifies the additional behavior of showing which documents they have or haven't signed. This distinguishes it from sibling tools like get-document-tool and get-group-tool, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving a single person and their signing status, which is distinct from list-people-tool (for multiple people) and get-document-tool (for document details). However, it does not explicitly state when to use this versus alternatives, so guidance is clear by implication but not spelled out.

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?