Skip to main content
Glama

place_world_tv

Place a virtual TV screen in a 3D world to play a Veo 3.1 video. Adjust position, rotation, and scale.

Instructions

Place a virtual TV screen in the 3D world playing a Veo 3.1 video.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_urlYes
xNo
yNo
zNo
rotation_yNo
scaleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only states the basic action without describing whether the TV is persistent, if it can be moved, or any side effects. The agent is left guessing about runtime behavior.

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 a single sentence, concise and front-loaded. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 6 parameters and no schema descriptions, the description is too sparse. An output schema exists but is not described. The tool's function is complex enough to warrant more details about placement, orientation, and results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It only mentions the video_url implicitly; none of the positional parameters (x, y, z, rotation_y, scale) are explained. The defaults in the schema are unhelpful without context.

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 tool's purpose: placing a virtual TV screen playing a Veo 3.1 video. It uses specific verbs and resources, and distinguishes from siblings, as no other tool mentions placing a TV.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. There are no prerequisites, context, or exclusionary conditions mentioned. The agent has no help deciding between this and other tools like spawn_agent_avatar or broadcast_spatial_audio.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/worldlabs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server