Skip to main content
Glama

overte_script_inject

Inject JavaScript to govern an Overte entity's behavior. Provide the entity UUID and script URL, with optional metadata, to apply custom in-world interactions.

Instructions

Inject a JavaScript script to govern behavior of an in-world entity.

Live when the Overte bridge WebSocket client is connected; otherwise returns a clearly labeled simulated confirmation.

Return Format

{"success": bool, "message": str, "data": {"source": str, "script": {...}}}

Examples

overte_script_inject(entity_id="abc-123-def", script_url="https://example.com/behavior.js") overte_script_inject(entity_id="abc-123-def", script_url="https://example.com/click.js", script_data={"color": "red"})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ctxNo
entity_idYesOverte target entity UUID.
script_urlYesJavaScript behavior script URL.
script_dataNoMetadata parameters to inject into the script scope.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral trait: the tool returns a clearly labeled simulated confirmation when disconnected, meaning it won't actually inject the script. It also specifies the return format, adding useful transparency beyond the bare existence of the tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: purpose statement, connectivity caveat, return format, and examples. It is concise without being terse, and each section earns its place. Slightly longer than necessary due to the return format and examples, but still efficiently organized.

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

Completeness4/5

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

Given the tool's moderate complexity, lack of annotations, and presence of an output schema, the description is quite complete. It explains the tool's purpose, the crucial live/simulation behavior, the return format, and provides instant-usage examples. It does not cover prerequisites or side effects, but these are not obviously critical for this tool.

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?

The schema already describes 3 of 4 parameters (75% coverage), providing a baseline of 3. The description adds value through examples showing how to pass entity_id, script_url, and script_data, but it leaves the 'ctx' parameter completely unexplained, so it doesn't fully compensate for the 25% schema gap.

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 specific action ('Inject a JavaScript script') and the target ('in-world entity'), along with the intended purpose ('to govern behavior'). This distinguishes it from sibling tools like overte_entity_spawn, which deals with entity creation.

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

Usage Guidelines4/5

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

The description provides important usage context by specifying that the tool is live only when the Overte bridge WebSocket client is connected, and otherwise returns a simulated confirmation. However, it does not explicitly discuss alternatives or when not to use the tool, so it falls short of a 5.

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/overte-mcp'

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