Skip to main content
Glama
extentos

extentos

injectHardwareButton

Inject a capture-button press to pause, resume, or stop the simulated glasses camera stream. Test app handling of paused or stopped camera states end-to-end.

Instructions

Press the simulated glasses' hardware CAPTURE BUTTON (the right-temple controls) — the agent's way to exercise the wearer's hardware privacy gestures with no human and no hardware. Tap on a LIVE camera stream pauses it; a second tap resumes. While paused, every stream-needing capture (capturePhoto — both mechanisms —, captureVideo, videoFrames) fails with CaptureError.StreamPaused carrying the actionable "tap the right temple to resume" message, and a capture_denied row lands in getEventLog(filter: 'errors') — the same behavior a wearer's temple tap produces on real glasses, because it IS the same shared gate. Hold STOPS the stream (camera_stream_closed): on real glasses the hold stops the whole device session — the connection drops and the SDK auto-recovers over ~3-5s; the sim closes the stream and deliberately skips the connection blip (a surfaced substrate delta) — the next frame-grab photo / video / videoFrames use re-arms it. The stream-state transitions land as camera_stream_opened / camera_stream_paused / camera_stream_resumed / camera_stream_closed under filter 'camera', and the sim page's capture LED tracks them (lit = streaming, dark = paused/closed); videoFrames delivery halts while paused and dies on close. A gesture with NO live stream is invisible to the app (hardware-faithful — it falls through to Meta's first-party capture, which DAT apps never see): arm the stream first. Mirrors the sim page's Hardware-buttons panel — same hub path, identical downstream. Typical loop: createSimulatorSession → ensureSimulatorBrowser → setSimVideo → (app takes a photo — stream arms) → injectHardwareButton (pause) → drive a capture → getEventLog(filter: 'errors') shows capture_denied → injectHardwareButton (resume) → capture succeeds. USE to test paused/stopped-camera handling end-to-end. DON'T USE for display input (injectInput), voice (injectTranscript), or hardware alerts like thermal/hinges (those inject via the sim page).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoThe press gesture. 'tap' = pause/resume toggle (StreamState PAUSED; no app-callable resume). 'hold' = stop the stream (on hardware the whole device session stops and the SDK auto-recovers; in the sim the stream closes and the next camera use re-arms it). This is the complete gesture set the glasses' capture button produces for third-party streams. Defaults to 'tap'.
buttonNoWhich hardware button to press. 'capture' (the right-temple capture button) only — the one button whose effect DAT surfaces to third-party apps. Defaults to 'capture'.
sessionIdYes
Behavior5/5

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

No annotations exist, so the description fully covers behavioral traits. It details the effects of tap vs hold, stream state transitions, error handling, differences from real hardware, and visual cues (LED). This is comprehensive transparency.

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 long but well-structured and front-loaded. Every sentence adds value, though some redundancy could be trimmed. However, the detail is justified given the complexity.

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 is complete for a tool with 3 parameters and no output schema. It covers input, behavior, side effects, error handling, and typical usage. No missing context.

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

Parameters5/5

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

The description adds significant meaning beyond the schema. It explains default values for action and button, the complete gesture set, and provides a typical usage loop. Schema coverage is 67%, but the description compensates fully with rich 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: pressing the simulated glasses' hardware capture button. It distinguishes this from sibling tools like injectInput and injectTranscript by specifying it's for hardware gestures, not display input or voice.

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 guidelines are provided: 'USE to test paused/stopped-camera handling end-to-end. DON'T USE for display input (injectInput), voice (injectTranscript), or hardware alerts.' Also includes a typical loop example, making it very clear when to use this tool.

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