agentView

Configure Display

configure_display

DestructiveIdempotent

Updates display settings: rename (name), lock or unlock content changes (locked), privacy mode for share links (privacy_mode), embed-origin allowlist (origins), hardware permissions (camera, microphone, geolocation), preferred language, mouse cursor, badge overlay and watermark position. Only the fields you pass are changed; online displays apply changes immediately. Use for any display setting change. Not for sending content (send_html, send_url) or deleting (delete_display). Requires admin scope.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	New display name (rename).
`locked`	No	true blocks content changes until unlocked; false unlocks.
`origins`	No	Embed-origin allowlist for Public displays; [] allows all origins.
`whitelist`	No	Domain whitelist for whitelist-only mode.
`display_id`	Yes	8-character display profile ID, e.g. 'ABCD1234'.
`access_token`	No	Optional bearer token; prefer session_request_id.
`allow_camera`	No
`privacy_mode`	No	Private caps share-link TTL at 1 hour; Public (signage mode) allows 24 hours.
`allow_microphone`	No
`strict_whitelist`	No	true: the display whitelist replaces the org whitelist instead of extending it.
`allow_geolocation`	No
`connectivity_mode`	No	Per-display network mode override.
`show_mouse_cursor`	No
`preferred_language`	No
`session_request_id`	No	Session handle from create_auth_session; pass it on every authenticated call.
`show_badge_overlay`	No
`watermark_position`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`name`	No
`allowCamera`	No
`allowMicrophone`	No
`changedSettings`	No
`showMouseCursor`	No
`allowGeolocation`	No
`showBadgeOverlay`	No
`effectiveLanguage`	No
`preferredLanguage`	No
`watermarkPosition`	No
`appliedToLiveDisplay`	No

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds meaningful behavioral context beyond annotations: partial updates, immediate effect for online displays, and the admin scope requirement. It doesn't contradict annotations and provides extra operational detail.

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-ordered: a list of settings up front, then behavior/constraints, then usage guidance. Every sentence contributes value without 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?

Given the tool's complexity (17 parameters, many boolean toggles), the description covers the essential behavior, scope, and known caveats. The output schema exists, so return format is not needed. The main missing details are some parameter descriptions, but those are already in the input schema, so the description is sufficiently complete for an agent to use correctly.

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 59%, so the description should compensate for undocumented parameters. It does explain many: rename, lock/unlock, privacy mode, origins, hardware permissions, language, cursor, badge, watermark. However, several parameters (whitelist, strict_whitelist, connectivity_mode, access_token, session_request_id) are not described, leaving some ambiguity that the schema partially offsets.

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 ('Updates'), the resource ('display settings'), and enumerates the specific settings. It explicitly distinguishes itself from sibling operations by naming what it is not for ('Not for sending content (send_html, send_url) or deleting (delete_display)').

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 states 'Use for any display setting change' and provides exclusions with alternative tool names. Also clarifies partial-update semantics ('Only the fields you pass are changed') and immediacy for online displays, which guides call timing.

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?