NexusAndroid

Overview Schema Source Related Servers Discussions Admin

phone

Read-onlyIdempotent

Verify Android device reachability over USB or Wi-Fi and return model, screen status, and foreground app for targeting actions.

Instructions

Link status: phone reached (USB or Wi-Fi), model, screen, foreground app.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`text`	Yes
`model`	Yes
`locked`	Yes
`serial`	Yes
`android`	Yes
`posture`	Yes	folded, half-open, open, or empty (non-foldable phone)
`rebooted`	Yes
`screen_on`	Yes
`transport`	Yes
`foreground`	Yes
`code_required`	Yes	locked and Android asks for the code (PIN, pattern, password, biometrics): only then the user must unlock it; false: look or the first gesture lifts the lock screen, no code
`kept_awake_until`	Yes	HH:MM, screen kept on by the agents until this time

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.16.0Oct 26, 2026

addedOutput schema / properties / code_required

Added value: +{
+  "description": "locked and Android asks for the code (PIN, pattern, password, biometrics): only then the user must unlock it; false: look or the first gesture lifts the lock screen, no code",
+  "title": "Code Required",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "text",
-  "model",
-  "serial",
-  "transport",
-  "android",
-  "posture",
-  "screen_on",
-  "locked",
-  "foreground",
-  "kept_awake_until",
-  "rebooted"
-]New value: +[
+  "text",
+  "model",
+  "serial",
+  "transport",
+  "android",
+  "posture",
+  "screen_on",
+  "locked",
+  "code_required",
+  "foreground",
+  "kept_awake_until",
+  "rebooted"
+]

Changed2 schema fields changedv0.9.3Oct 22, 2026

changedOutput schema / properties / kept_awake_until / description

Previous value: -"HH:MM, écran gardé allumé par les agents jusqu'à cette heure"New value: +"HH:MM, screen kept on by the agents until this time"

changedOutput schema / properties / posture / description

Previous value: -"plié, entrouvert, ouvert ou vide (téléphone non pliable)"New value: +"folded, half-open, open, or empty (non-foldable phone)"

Changed1 schema field changedv0.4.1Oct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "android": {
+      "title": "Android",
+      "type": "string"
+    },
+    "foreground": {
+      "title": "Foreground",
+      "type": "string"
+    },
+    "kept_awake_until": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "HH:MM, écran gardé allumé par les agents jusqu'à cette heure",
+      "title": "Kept Awake Until"
+    },
+    "locked": {
+      "title": "Locked",
+      "type": "boolean"
+    },
+    "model": {
+      "title": "Model",
+      "type": "string"
+    },
+    "posture": {
+      "description": "plié, entrouvert, ouvert ou vide (téléphone non pliable)",
+      "title": "Posture",
+      "type": "string"
+    },
+    "rebooted": {
+      "title": "Rebooted",
+      "type": "boolean"
+    },
+    "screen_on": {
+      "title": "Screen On",
+      "type": "boolean"
+    },
+    "serial": {
+      "title": "Serial",
+      "type": "string"
+    },
+    "text": {
+      "title": "Text",
+      "type": "string"
+    },
+    "transport": {
+      "enum": [
+        "usb",
+        "wifi"
+      ],
+      "title": "Transport",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text",
+    "model",
+    "serial",
+    "transport",
+    "android",
+    "posture",
+    "screen_on",
+    "locked",
+    "foreground",
+    "kept_awake_until",
+    "rebooted"
+  ],
+  "title": "PhoneStatus",
+  "type": "object"
+}

First observedv0.3.1Oct 17, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description's only added signal is the transport distinction (USB or Wi-Fi) and the fact that device/app state is observed, which is modest extra context.

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 short fragment with no padding and the key concept ('Link status') front-loaded. It is arguably over-compressed into a field list rather than a sentence, but nothing is wasteful.

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?

An output schema exists, so enumerating return values in the description is largely redundant and the description does not spend that space on what it uniquely should: when this status check is appropriate and what a failure/offline result means. For a zero-param read-only tool this is close to sufficient, but not quite.

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?

The tool takes zero parameters, which is the baseline-4 case; no parameter explanation is required. The description also implies the scope of reported state, though that overlaps with the output schema.

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

Purpose3/5

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

The description is a noun-phrase list of return fields ('Link status: phone reached (USB or Wi-Fi), model, screen, foreground app') rather than a verb+resource statement. An agent can infer it reports the phone link/connection status, but the framing is ambiguous and it never distinguishes itself from siblings like info, checkup, or look.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus alternatives, nor any precondition such as requiring the phone link to be active. The agent must infer usage entirely from the tool name and one fragment of prose.

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

Deploy Server