Skip to main content
Glama
pironjulien

NexusAndroid

by pironjulien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

look

Read-onlyIdempotent

Retrieves Android phone screen elements and images as numbered UI trees and screenshots for AI agents to inspect, query, and zoom regions in NexusAndroid.

Instructions

Voir l'écran du téléphone : éléments numérotés [N] (rôle, texte, états, centre @x,y) et image. show : both (défaut), image, elements, none. query : ne lister que les éléments contenant ce texte. region [x1,y1,x2,y2] : zoom (pixels de la dernière image complète). Arbre UI illisible : l'image n'est pas envoyée (codes non masqués), sauf confirm=true, posé seulement avec l'accord de l'utilisateur.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
showNoboth
queryNo
regionNo
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • addedInput schema / properties / confirm
      Added value: +{
+  "default": false,
+  "title": "Confirm",
+  "type": "boolean"
+}
  2. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's value is the extra behaviour it discloses: the numbered-element return shape, the privacy fallback where the image is withheld when the UI tree is unreadable, and the consent requirement for confirm. That is real context an agent cannot get from the annotations, though the phrasing of the fallback is cryptic.

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?

Purpose is front-loaded in the first clause, then each parameter is dispatched in a short fragment. No filler sentences; density is high without being padded.

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?

For a 4-parameter, zero-coverage, read-only tool with no output schema, the description covers return format, every parameter, and the safety fallback. What is missing is routing against the ten siblings and any note that this is the observation step preceding act.

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 0%, so the description must carry the load and largely does: show modes with the default, query as a text filter over listed elements, region as a zoom box measured in pixels of the last full image, and confirm tied to user consent. Only confirm's exact effect remains under-specified.

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 concrete verb and resource ('Voir l'écran du téléphone') and describes the payload precisely: numbered elements with role, text, states and centre coordinates, plus an image. It is clearly the observation tool among siblings like act and launch, though it never names a sibling explicitly.

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 only real when-to-use rule is for confirm ('posé seulement avec l'accord de l'utilisateur'), which is genuinely useful. The show/query/region text explains what each option does but not when to prefer look over act or info, and there are no exclusions or prerequisite (e.g. must call before act) guidance.

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