Skip to main content
Glama
extentos

extentos

injectInput

Drive simulated glasses display: select items to fire onClick, navigate focus, or send back. Enables end-to-end testing of display handlers without hardware.

Instructions

Drive the simulated glasses' DISPLAY input — the agent's way to "click" the display with no human and no hardware (track 5). Three actions: select (+ targetId) fires that node's onClick, running the developer's handler exactly as a Neural-Band index-pinch would on real glasses — THE action that closes the display E2E loop; navigate (+ optional targetId) moves the focus highlight (to a specific id, or the next selectable node when omitted); back emits a back gesture. The frame is delivered to the simulator browser tab (the display surrogate that owns the rendered tree + focus), which routes the selection back to the app — so an agent-injected select and a human clicking the sim's gesture panel are identical downstream (selection flows browser → backend → app, mirroring real hardware). Requires the simulator browser tab connected — the display only exists while the browser renders it; call ensureSimulatorBrowser({ sessionId }) first or this returns browser_not_connected. Discover targetId values from getDisplayState.interactiveIds. Typical loop: createSimulatorSession → ensureSimulatorBrowser → (app shows a display) → getDisplayState → injectInput({ action: 'select', targetId: 'end-run' })getEventLog(filter: 'display') shows display_select then the re-render (display_show). Mirrors injectTranscript (voice) / setSimVideo (camera) for the display capability. USE to exercise display button handlers + navigation end-to-end. DON'T USE for voice flows (injectTranscript / injectAssistantUtterance) or to read display state (getDisplayState).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes'select' fires the target (or focused) node's onClick — pass targetId (from getDisplayState.interactiveIds) for a deterministic click. 'navigate' moves the focus highlight to targetId, or to the next selectable node when targetId is omitted. 'back' emits a back gesture (an event; the dev owns 'views' via successive show() calls).
targetIdNoThe node id to target. For 'select', the button/container id whose onClick should fire (strongly recommended — get it from getDisplayState.interactiveIds; omit to select the currently-focused node). For 'navigate', the id to focus (omit to advance to the next focusable). Ignored for 'back'.
sessionIdYes
Behavior5/5

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

With no annotations, the description fully bears the burden. It details each action's effect (select fires onClick, navigate moves focus, back emits back gesture) and the downstream flow mirroring real hardware. Error conditions (browser_not_connected) and relationships to other capabilities are also disclosed.

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 lengthy but well-structured with bolded action names and a bullet-like layout. It front-loads the core purpose and packs necessary details. Minor redundancy exists, but every sentence serves a purpose.

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?

The description covers prerequisites, typical loop, error conditions, and relationships to other tools. It provides enough context for an agent to use this complex tool correctly without an output schema.

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 description coverage is 67%, and the description adds significant value beyond the schema: it explains where to get targetId values, the effect of omitting it for navigate, and the role of sessionId in the typical loop. However, sessionId itself is not elaborately described.

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: driving simulated glasses display input as an agent's way to 'click' the display. It names three specific actions (select, navigate, back) and distinguishes itself from sibling tools like injectTranscript and setSimVideo.

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?

Explicit usage guidance is provided: 'USE to exercise display button handlers + navigation end-to-end. DON'T USE for voice flows... or to read display state.' It also gives a prerequisite (call ensureSimulatorBrowser first) and a typical loop, making when-to-use and when-not-to-use very clear.

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/extentos/mcp-server'

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