ClearPolicy

Get Group Tool

get-group-tool

Read-onlyIdempotent

Get details for one ClearPolicy group, including counts and resource URIs for its members and documents.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`group_id`	Yes	The ULID of the group to retrieve.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`source`	No
`app_url`	Yes
`source_id`	No
`created_at`	No
`updated_at`	No
`description`	No
`resource_uri`	Yes
`last_synced_at`	No
`documents_count`	Yes
`recipient_message`	No
`active_people_count`	Yes
`members_resource_uri`	Yes
`compliant_people_count`	Yes
`documents_resource_uri`	Yes
`automatic_request_issuance_enabled`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 17, 2026

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

changedOutput schema / required

Previous value: -[
-  "id",
-  "name",
-  "automatic_request_issuance_enabled",
-  "active_people_count",
-  "compliant_people_count",
-  "documents_count",
-  "resource_uri",
-  "members_resource_uri",
-  "documents_resource_uri"
-]New value: +[
+  "id",
+  "name",
+  "automatic_request_issuance_enabled",
+  "active_people_count",
+  "compliant_people_count",
+  "documents_count",
+  "resource_uri",
+  "app_url",
+  "members_resource_uri",
+  "documents_resource_uri"
+]

Changed1 schema field changedJul 2, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "active_people_count": {
+      "type": "integer"
+    },
+    "automatic_request_issuance_enabled": {
+      "type": "boolean"
+    },
+    "compliant_people_count": {
+      "type": "integer"
+    },
+    "created_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "documents_count": {
+      "type": "integer"
+    },
+    "documents_resource_uri": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "last_synced_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "members_resource_uri": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "recipient_message": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "resource_uri": {
+      "type": "string"
+    },
+    "source": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "updated_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "automatic_request_issuance_enabled",
+    "active_people_count",
+    "compliant_people_count",
+    "documents_count",
+    "resource_uri",
+    "members_resource_uri",
+    "documents_resource_uri"
+  ],
+  "type": "object"
+}

AddedApr 27, 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 and destructiveHint=false. Description adds useful context about return content (counts, resource URIs) beyond annotations, but does not describe other behavioral traits like pagination or authentication.

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?

Single sentence, front-loaded with key information, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given single required parameter, full annotations, and presence of output schema, description sufficiently covers purpose and return details (counts, URIs).

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% and description does not add meaning beyond the schema's parameter description ('The ULID of the group to retrieve'). Baseline 3 applies.

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?

Description clearly states verb 'Get', resource 'ClearPolicy group', and specifies inclusions ('counts and resource URIs for its members and documents'). Distinct from sibling tools like list-groups-tool (listing all) and get-person-tool (different resource).

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?

No explicit guidance on when to use this tool versus alternatives (e.g., list-groups-tool). Usage is implied by name and description but not stated.

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?