agentView

Set Display Grant

set_display_grant

DestructiveIdempotent

Grants or revokes a member's access to one display inside an organization. action 'set' (default) creates/updates the grant with access_level 'view' (see status) or 'control' (send content); action 'remove' revokes it. The target user must be an organization member. Requires admin scope.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	No	'set' (default) creates/updates the grant; 'remove' revokes it.
`org_id`	Yes	Organization ID.
`display_id`	Yes	Display profile ID.
`access_level`	No	Required for action 'set'.
`access_token`	No	Optional bearer token; prefer session_request_id.
`target_user_id`	Yes	User to grant or revoke.
`session_request_id`	No	Session handle from create_auth_session; pass it on every authenticated call.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`granted`	No
`removed`	No
`displayId`	No
`accessLevel`	No
`targetUserId`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accessLevel": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "displayId": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "granted": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "removed": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "targetUserId": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed9 schema fields changedJul 6, 2026

changedInput schema / properties / access_level / description

Previous value: -"Access level: 'view' or 'control'."New value: +"Required for action 'set'."

changedInput schema / properties / access_token / description

Previous value: -"Optional JWT access token for authentication."New value: +"Optional bearer token; prefer session_request_id."

addedInput schema / properties / action

Added value: +{
+  "description": "'set' (default) creates/updates the grant; 'remove' revokes it.",
+  "enum": [
+    "set",
+    "remove"
+  ],
+  "type": "string"
+}

changedInput schema / properties / display_id / description

Previous value: -"The display profile ID."New value: +"Display profile ID."

changedInput schema / properties / org_id / description

Previous value: -"The organization ID."New value: +"Organization ID."

addedInput schema / properties / session_request_id

Added value: +{
+  "description": "Session handle from create_auth_session; pass it on every authenticated call.",
+  "type": "string"
+}

changedInput schema / properties / target_user_id / description

Previous value: -"The user ID to grant access to."New value: +"User to grant or revoke."

changedInput schema / required

Previous value: -[
-  "org_id",
-  "display_id",
-  "target_user_id",
-  "access_level"
-]New value: +[
+  "org_id",
+  "display_id",
+  "target_user_id"
+]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "accessLevel": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "displayId": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "granted": {
-      "type": [
-        "boolean",
-        "null"
-      ]
-    },
-    "targetUserId": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed4 schema fields changedJun 2, 2026

changedOutput schema / properties / accessLevel / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / displayId / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / granted / type

Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]

changedOutput schema / properties / targetUserId / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

Changed4 schema fields changedMay 23, 2026

addedInput schema / properties / access_level / enum
```
Added value: +[
+  "view",
+  "control"
+]
```
removedInput schema / properties / access_token / default
```
Removed value: -null
```

changedInput schema / properties / access_token / type

Previous value: -[
-  "string",
-  "null"
-]New value: +"string"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accessLevel": {
+      "type": "string"
+    },
+    "displayId": {
+      "type": "string"
+    },
+    "granted": {
+      "type": "boolean"
+    },
+    "targetUserId": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the mutation/destructive nature is covered. The description adds meaningful context beyond annotations by explaining what 'set' and 'remove' do, defining access levels, and stating the admin scope requirement. No contradiction with annotations.

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?

Three concise sentences cover purpose, actions, access levels, prerequisites, and permissions without any filler. The main purpose is front-loaded, and every sentence earns its place.

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?

Given the output schema exists, return values do not need to be explained. The description covers the required member condition, admin scope, action semantics, and access-level meanings. It is slightly light on what happens if access_level is provided with action 'remove', but this is a minor edge case given the schema already marks it as only required for 'set'.

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 coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining the 'view' access level as 'see status' and 'control' as 'send content', and by clarifying the default behavior of 'action'. This adds useful meaning not present in the parameter descriptions.

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 uses a specific verb ('Grants or revokes') and names the exact resource ('a member's access to one display inside an organization'). It clearly distinguishes this from sibling tools like manage_org_member or assign_display_categories by focusing on display-level grants.

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 provides clear context: it explains the default action, the two actions, and explicitly states prerequisites ('target user must be an organization member' and 'Requires admin scope'). It does not explicitly name alternatives or say when not to use it, but the provided conditions are sufficient for an agent to infer appropriate usage.

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

All agentView tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools map cleanly to distinct resource-action pairs (displays, organizations, assets, data slots, store templates, auth). A few clusters like the get_store_template_* family and the auth/session tools could still confuse an agent, but their descriptions are explicit enough to separate them.

Naming Consistency4/5

The dominant pattern is consistent verb_noun snake_case (list_*, get_*, create_*, delete_*, send_*, set_*, manage_*). Deviations like fetch, search, authenticate, logout, and pair_by_code are understandable but break the otherwise uniform naming scheme.

Tool Count1/5

With 57 tools this server far exceeds the 50+ threshold, creating an extreme tool-set size for an MCP server. Even though the underlying platform is feature-rich, the sheer number of tools heavily taxes context and selection.

Completeness4/5

The surface covers display, organization, asset, data slot, store template, auth, API key, and licensing lifecycles in impressive depth. Minor gaps exist, such as no delete operation for display categories and no reboot/power control for displays.

Resources

Need Help?