agentView

Create Display

create_display

Pre-provisions a display without hardware, personal or inside an organization (org_id). The new display starts offline. For a physical screen ALWAYS prefer pair_by_code, which creates and pairs in one step; use create_display only to prepare a display before the screen exists or for virtual/API-only displays. Requires admin scope. Returns id plus setup and pairing URLs.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Friendly display name, e.g. 'Lobby Screen'. Required when org_id is set.
`org_id`	No	Optional: create the display inside this organization (needs manager role and a free license slot).
`access_token`	No	Optional bearer token; prefer session_request_id.
`session_request_id`	No	Session handle from create_auth_session; pass it on every authenticated call.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`name`	No
`status`	No
`setupUrl`	No
`managedUrl`	No
`pairingUrl`	No
`approvalUrl`	No
`pairingExpiresAt`	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": {
+    "approvalUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "managedUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "name": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pairingExpiresAt": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pairingUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "setupUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedJul 6, 2026

changedInput schema / properties / access_token / description

Previous value: -"Optional bearer credential. Prefer passing session_request_id (from create_auth_session) instead; every tool accepts it and the server resolves it to your identity server-side. Use access_token only when you hold an OAuth bearer token and your MCP client cannot send it as an Authorization: Bearer HTTP header automatically."New value: +"Optional bearer token; prefer session_request_id."

changedInput schema / properties / name / description

Previous value: -"Optional friendly name for the new display. If omitted, a default name is assigned. Example: 'Lobby Screen'."New value: +"Friendly display name, e.g. 'Lobby Screen'. Required when org_id is set."

addedInput schema / properties / org_id

Added value: +{
+  "description": "Optional: create the display inside this organization (needs manager role and a free license slot).",
+  "type": "string"
+}

addedInput schema / properties / session_request_id

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

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "approvalUrl": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "id": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "managedUrl": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "name": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "pairingExpiresAt": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "pairingUrl": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "setupUrl": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "status": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed8 schema fields changedJun 2, 2026

changedOutput schema / properties / approvalUrl / type

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

changedOutput schema / properties / id / type

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

changedOutput schema / properties / managedUrl / type

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

changedOutput schema / properties / name / type

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

changedOutput schema / properties / pairingExpiresAt / type

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

changedOutput schema / properties / pairingUrl / type

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

changedOutput schema / properties / setupUrl / type

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

changedOutput schema / properties / status / type

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

Changed1 schema field changedMay 30, 2026

changedInput schema / properties / access_token / description

Previous value: -"Optional JWT access token for authentication. Pass the token returned by get_auth_session when your MCP client does not send it as an Authorization: Bearer HTTP header automatically."New value: +"Optional bearer credential. Prefer passing session_request_id (from create_auth_session) instead; every tool accepts it and the server resolves it to your identity server-side. Use access_token only when you hold an OAuth bearer token and your MCP client cannot send it as an Authorization: Bearer HTTP header automatically."

Changed6 schema fields changedMay 23, 2026

removedInput schema / properties / access_token / default
```
Removed value: -null
```

changedInput schema / properties / access_token / type

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

removedInput schema / properties / name / default
```
Removed value: -null
```

changedInput schema / properties / name / type

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

removedInput schema / properties / session_request_id

Removed value: -{
-  "default": null,
-  "description": "Optional session request ID returned by create_auth_session. Pass this instead of access_token for simpler, more reliable authentication — the server resolves the identity server-side.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "approvalUrl": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "managedUrl": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "pairingExpiresAt": {
+      "type": "string"
+    },
+    "pairingUrl": {
+      "type": "string"
+    },
+    "setupUrl": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond annotations, the description discloses that the new display starts offline, requires admin scope, and returns setup and pairing URLs. This adds meaningful behavioral context. It doesn't describe all edge cases, but the annotations already cover read-only, destructive, open-world, and idempotency traits.

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 compact and well-structured: it states the core purpose first, then usage guidance, then access requirements and return value. Every sentence earns its place with no redundancy.

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?

For a tool with this complexity, the description covers purpose, when to use, auth requirement, initial state, and return payload. Combined with the fully documented schema and output schema, nothing essential is missing for an agent to invoke it 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%, so the parameters are fully documented in the schema. The description adds some semantic value by mentioning org_id and the pairing URL return, but it does not need to explain each parameter further.

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–resource pair ('Pre-provisions a display') and clarifies that the display is created without hardware, either personally or in an organization. It explicitly distinguishes itself from pair_by_code, so the agent can confidently differentiate it from the closest sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description gives explicit guidance: for physical screens ALWAYS prefer pair_by_code, and create_display should only be used to prepare a display before hardware exists or for virtual/API-only displays. This clearly states when to use and when not to use the tool, naming the alternative.

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?