Skip to main content
Glama
software-mansion

Argent

Official
by software-mansion
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

native-user-interactable-view-at-point

Find the deepest touch-responsive view at a raw screen point, respecting userInteractionEnabled, to debug unexpected taps or unresponsive controls.

Instructions

Inspect the deepest UIView at a raw native window point that would actually receive touch input.

Unlike native-view-at-point, this respects userInteractionEnabled and is closer to UIKit hit-testing semantics.

Use when a tap lands somewhere unexpected or does nothing, to see which control UIKit would hand the touch to — a transparent overlay swallowing it, a parent recognizer, a disabled button.

Returns { status: "ok", view }: the hit-test winner with its class name, frames, identifier, label and layer name, its ancestor chain by default, and its subviews on request. view is null when no touchable view sits under that point.

IMPORTANT: x and y are raw points on the portrait axes of the screen, NOT normalized [0,1] simulator tap coordinates. To get them from a describe frame, multiply the normalized values by the screen size in points. Do this also when the UI is landscape.

If status is restart_required: follow the message (usually restart-app), then retry. If status is service_stale: the app is already injected, so restarting it cannot help — restart the tool-server (argent server stop && argent server start --detach) and retry. If the same status comes back after that restart, stop restarting: follow the message, which names the terminal fallback. If status is connect_pending: the app is injected and still connecting — do not restart it, wait a few seconds and retry. If status is init_failed: the simulator's native-devtools environment could not be initialised — follow the message (re-boot the simulator) rather than retrying this tool. A not-connected or not-running app comes back as one of those statuses rather than a failure. Failures are separate: an Apple system app is rejected outright (terminal — never retry it), and the point query itself can error or time out.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesRaw X coordinate in points, on the portrait axes of the screen (the axes of native-describe-screen frames). NOT normalized [0,1] tap space.
yYesRaw Y coordinate in points, on the portrait axes of the screen (the axes of native-describe-screen frames). NOT normalized [0,1] tap space.
udidYesSimulator UDID
fieldsNoView fields to include. Defaults: pointer, className, tag, frame, windowFrame, screenFrame, bounds, hidden, alpha, opaque, clipsToBounds, userInteractionEnabled, depth, identifier, label, layerName, nativeID. Additional: center, transform, contentMode, backgroundColor, tintColor
bundleIdYesBundle ID of the app
maxDepthNoMaximum depth for returned child/ancestor serialization (default 150)
skipClassesNoExact UIView class names whose entire subtree should be pruned
includeChildrenNoInclude child views for the matched view (default false)
includeAncestorsNoInclude ancestor chain for the matched view (default true)
skipClassPrefixesNoClass name prefixes to prune entire subtrees

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.26.0
    • changedInput schema / properties / fields / description
      Previous value: -"View fields to include. Defaults: pointer, className, tag, frame, windowFrame, bounds, hidden, alpha, opaque, clipsToBounds, userInteractionEnabled, depth, identifier, label, layerName, nativeID. Additional: center, transform, contentMode, backgroundColor, tintColor"New value: +"View fields to include. Defaults: pointer, className, tag, frame, windowFrame, screenFrame, bounds, hidden, alpha, opaque, clipsToBounds, userInteractionEnabled, depth, identifier, label, layerName, nativeID. Additional: center, transform, contentMode, backgroundColor, tintColor"
    • changedInput schema / properties / x / description
      Previous value: -"Raw X coordinate in the app window's native point space. NOT normalized [0,1] tap space."New value: +"Raw X coordinate in points, on the portrait axes of the screen (the axes of native-describe-screen frames). NOT normalized [0,1] tap space."
    • changedInput schema / properties / y / description
      Previous value: -"Raw Y coordinate in the app window's native point space. NOT normalized [0,1] tap space."New value: +"Raw Y coordinate in points, on the portrait axes of the screen (the axes of native-describe-screen frames). NOT normalized [0,1] tap space."
  2. First observedv0.15.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries full behavioral disclosure. It details return shape with statuses, null behavior, coordinate-axis semantics, and the exact meaning of restart_required, service_stale, connect_pending, and init_failed, including fallback actions. This goes far beyond what the schema reports.

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 long but front-loaded: purpose first, sibling distinction second, then use case, return contract, coordinate warning, and status handling. Each section earns its place given the tool's complexity and lack of annotations.

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?

For a 10-parameter tool with no annotations and no output schema, the description covers the full call contract: what is returned, when view is null, coordinate conversion, status recovery procedures, and permanent failure cases. An agent has what it needs to invoke the tool correctly.

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 the baseline is 3; the description adds meaningful value above the schema by explaining that x/y are raw portrait-axis points, NOT normalized [0,1] tap coordinates, and how to convert from describe frames. It also summarizes field defaults, though those are also listed in the schema.

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 opens with a specific verb and resource: 'Inspect the deepest UIView at a raw native window point that would actually receive touch input.' It then differentiates from native-view-at-point by noting it respects userInteractionEnabled and follows UIKit hit-testing semantics, so an agent can distinguish it from the closest sibling.

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?

It gives explicit when-to-use guidance: 'Use when a tap lands somewhere unexpected or does nothing...' and names the alternative (native-view-at-point) as the non-hit-testing variant. It also tells when not to retry the tool, e.g., Apple system apps are rejected outright and restarting cannot help for service_stale.

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

Deploy Server

Other Tools