Skip to main content
Glama

agentView

by de.agentview
OverviewDiscussionsAdmin

Create Display

create_display

Creates a display and returns managedUrl, a permanent link that turns whatever browser opens it into that screen. This is the DEFAULT way to a first screen: create, give the user the managedUrl to open on a device they already have (the phone in their hand, a tablet, a spare monitor, a second tab), then send content so they see a real page at once. It asks them to walk nowhere. Prefer pair_by_code only when they are standing at a dedicated screen (TV, wall panel, kiosk) already showing a 6-character code. Optionally creates inside an organization (org_id). Requires mcp:display.setup, granted to connectors on connection; NOT full admin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFriendly display name, e.g. 'Lobby Screen'. Required when org_id is set.
org_idNoOptional: create the display inside this organization (needs manager role and a free license slot).
access_tokenNoOptional bearer token; prefer session_request_id.
session_request_idNoSession handle from create_auth_session; pass it on every authenticated call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
nameNo
statusNo
setupUrlNo
managedUrlNo
pairingUrlNo
approvalUrlNo
pairingExpiresAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed5 schema fields changed
    • 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
  3. Changed8 schema fields changed
    • 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"
+]
  4. Changed1 schema field changed
    • 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."
  5. Changed6 schema fields changed
    • 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"
+}
  6. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare this is not read-only, not destructive, non-idempotent, and closed-world. The description adds important permission context: requires mcp:display.setup, granted to connectors on connection, and NOT full admin. It also explains the practical effect of the returned managedUrl.

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?

Front-loads what the tool does and returns before giving routing guidance. The sentences are purposeful: they cover default usage, the alternative, optional org creation, and permission requirements without burying the key details.

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?

Complete for this tool given the rich schema, annotations, and output schema. It explains when to use it, when to use the alternative, permission expectations, and the meaning of the managedUrl return value.

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 schema already documents all four parameters, including org_id requirements and auth alternatives. The description adds only limited parameter-level meaning beyond the schema, such as restating that org_id is optional.

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?

States a specific verb and resource ('Creates a display') and immediately clarifies the key output: managedUrl, a permanent link that turns the opening browser into that screen. It also distinguishes itself from the sibling pair_by_code by describing the default create-first screen setup flow.

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?

Explicitly says this is the DEFAULT way to set up a first screen and gives the exact condition for preferring pair_by_code: only when the user is standing at a dedicated screen already showing a 6-character code. It also notes optional org-scoped creation and the required permission.

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

All agentView toolsInspect
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