Skip to main content
Glama

tap_focused

Focuses a referenced TV UI element and presses SELECT in one step, so agents can activate controls during live device verification.

Instructions

TV: move focus to an element and press SELECT in one step.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ref": "<ref>"
    },
    "name": "tap_focused"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesRef from the UI tree (e.g. @e5).
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint=false annotation already flags this as a mutating action, and the description is consistent with that by disclosing that SELECT is pressed. It adds the composite nature (focus + activate) but says nothing about failure modes, whether focus failures abort the press, or what state the TV is left in — useful but thin given the minimal annotation set.

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?

A single front-loaded sentence with no filler; the two sub-actions are ordered exactly as they execute. Minor deduction because the leading 'TV:' token is cryptic and takes space without clarifying the platform constraint.

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

Completeness3/5

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

For a two-parameter, no-output-schema tool this covers the core behavior, but an agent cannot tell what happens when the element is missing or unfocusable, nor whether the press result is reported back. Given only a single readOnlyHint annotation, a sentence on outcome/error behavior would round it out.

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 coverage is 100%, so both ref and session_id are fully documented in the schema, including the fallback chain for session resolution. The description reinforces that the target is 'an element' (i.e., a ref from the UI tree) without adding syntax beyond the schema, so baseline-plus credit applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific composite action (move focus to an element then press SELECT) and scopes it to TV targets, which distinguishes it reasonably well from the sibling focus, press and tap tools. The 'TV:' prefix is a terse shorthand that assumes the agent knows the platform split, but the verb+resource statement itself is unambiguous.

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

Usage Guidelines3/5

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

The phrase 'in one step' implies this is the batched alternative to calling focus followed by press, but the description never names that alternative or states conditions for choosing it over tap or focus+press. Usage is inferable rather than stated, so this sits at minimum-viable.

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