agentView

Send URL

send_url

Destructive

Shows an external web page on a display via full-page iframe: dashboards, websites or web apps. slot 'live' (default) replaces current content; slot 'idle' stores it as default/fallback content (admin scope). The URL must be absolute HTTP(S). Check get_display (response_format 'detailed') first when unsure about connectivity or embedding limits. If the page design is not display-ready, prefer send_html with generated content. Requires content scope.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Absolute HTTP or HTTPS URL to load, e.g. 'https://example.com/dashboard'.
`slot`	No	'live' (default) or 'idle' for default/fallback content (admin scope).
`duration`	No	Seconds the content stays; 0 = indefinite (default). Live slot only.
`display_id`	Yes	8-character display profile ID, e.g. 'ABCD1234'.
`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.
`content_description`	No	Short summary of what the page shows (recommended).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No
`name`	No
`idleFile`	No
`idleVersion`	No
`idleContentCleared`	No

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds meaningful behavioral context: slot 'live' replaces current content, slot 'idle' stores default/fallback content, requires content scope, and URL must be absolute HTTP(S). It stops short of explicitly stating irreversibility or consequences of replacement, but 'replaces' plus the destructive annotation cover the core side effect.

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 three compact sentences with the core action and slot behavior front-loaded. Every sentence earns its place: purpose, operational constraints, and usage guidance. There is no filler or redundant repetition.

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 rich schema coverage and output schema, the description provides the missing operational context: slot semantics, scope requirement, URL constraints, and when to check get_display or switch to send_html. Nothing essential for an agent to call this tool correctly is absent.

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 carries the parameter documentation burden. The description mostly restates slot semantics and the absolute-URL constraint that already appear in the schema, adding little new parameter-level meaning beyond the general guidance to prefer send_html for non-display-ready pages.

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 names a specific verb ('Shows'), a specific resource ('external web page on a display'), and the mechanism ('full-page iframe'). It also distinguishes the intent from the sibling send_html by noting it is for display-ready dashboards/websites/web apps, so an agent can tell this tool apart at a glance.

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 routing guidance: check get_display (response_format 'detailed') when unsure about connectivity or embedding limits, and prefer send_html when the page design is not display-ready. It also states the content scope requirement, leaving little to inference.

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?