NexusAndroid

Overview Schema Source Related Servers Discussions Admin

info

Read-onlyIdempotent

Retrieves read-only Android data—last known location, recent calls, contact numbers, and upcoming calendar events—so agents can answer user queries.

Instructions

Read-only. location: last known position (accuracy, age, Maps link). calls: recent calls (incoming, outgoing, missed). contacts: numbers for a name (query). calendar: events of the next days days.

Input Schema

Name	Required	Description	Default
`days`	No
`kind`	Yes
`limit`	No
`query`	No

Output Schema

Name	Required	Description	Default
`kind`	Yes
`text`	Yes
`calls`	No
`events`	No
`contacts`	No
`location`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.9.3Oct 22, 2026

changedOutput schema / $defs / Call / properties / date / description

Previous value: -"ISO 8601, heure locale du PC"New value: +"ISO 8601, PC local time"

changedOutput schema / $defs / Call / properties / type / description

Previous value: -"reçu, émis, manqué, messagerie, refusé, bloqué"New value: +"incoming, outgoing, missed, voicemail, rejected, blocked"

changedOutput schema / description

Previous value: -"Réponse structurée de info : le champ du `kind` demandé est rempli, le texte reprend tout."New value: +"Structured response of info: the field of the requested `kind` is filled, the text repeats everything."

Changed1 schema field changedv0.4.1Oct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "Call": {
+      "properties": {
+        "date": {
+          "description": "ISO 8601, heure locale du PC",
+          "title": "Date",
+          "type": "string"
+        },
+        "duration_s": {
+          "title": "Duration S",
+          "type": "integer"
+        },
+        "number": {
+          "title": "Number",
+          "type": "string"
+        },
+        "type": {
+          "description": "reçu, émis, manqué, messagerie, refusé, bloqué",
+          "title": "Type",
+          "type": "string"
+        },
+        "who": {
+          "title": "Who",
+          "type": "string"
+        }
+      },
+      "required": [
+        "date",
+        "type",
+        "who",
+        "number",
+        "duration_s"
+      ],
+      "title": "Call",
+      "type": "object"
+    },
+    "Contact": {
+      "properties": {
+        "name": {
+          "title": "Name",
+          "type": "string"
+        },
+        "number": {
+          "title": "Number",
+          "type": "string"
+        }
+      },
+      "required": [
+        "name",
+        "number"
+      ],
+      "title": "Contact",
+      "type": "object"
+    },
+    "Event": {
+      "properties": {
+        "all_day": {
+          "title": "All Day",
+          "type": "boolean"
+        },
+        "begin": {
+          "title": "Begin",
+          "type": "string"
+        },
+        "end": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "title": "End"
+        },
+        "location": {
+          "title": "Location",
+          "type": "string"
+        },
+        "title": {
+          "title": "Title",
+          "type": "string"
+        }
+      },
+      "required": [
+        "begin",
+        "end",
+        "all_day",
+        "title",
+        "location"
+      ],
+      "title": "Event",
+      "type": "object"
+    },
+    "Location": {
+      "properties": {
+        "accuracy_m": {
+          "title": "Accuracy M",
+          "type": "integer"
+        },
+        "age_s": {
+          "title": "Age S",
+          "type": "integer"
+        },
+        "latitude": {
+          "title": "Latitude",
+          "type": "number"
+        },
+        "longitude": {
+          "title": "Longitude",
+          "type": "number"
+        },
+        "maps_url": {
+          "title": "Maps Url",
+          "type": "string"
+        }
+      },
+      "required": [
+        "latitude",
+        "longitude",
+        "accuracy_m",
+        "age_s",
+        "maps_url"
+      ],
+      "title": "Location",
+      "type": "object"
+    }
+  },
+  "description": "Réponse structurée de info : le champ du `kind` demandé est rempli, le texte reprend tout.",
+  "properties": {
+    "calls": {
+      "items": {
+        "$ref": "#/$defs/Call"
+      },
+      "title": "Calls",
+      "type": "array"
+    },
+    "contacts": {
+      "items": {
+        "$ref": "#/$defs/Contact"
+      },
+      "title": "Contacts",
+      "type": "array"
+    },
+    "events": {
+      "items": {
+        "$ref": "#/$defs/Event"
+      },
+      "title": "Events",
+      "type": "array"
+    },
+    "kind": {
+      "enum": [
+        "location",
+        "calls",
+        "contacts",
+        "calendar"
+      ],
+      "title": "Kind",
+      "type": "string"
+    },
+    "location": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/Location"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null
+    },
+    "text": {
+      "title": "Text",
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "text"
+  ],
+  "title": "InfoResult",
+  "type": "object"
+}

First observedv0.3.1Oct 17, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful context about what each kind returns, such as location accuracy/age/Maps link and calendar events over `days`, but it omits defaults, limits, permissions, and query-matching behavior.

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 compact and front-loads the read-only nature before listing each kind. It is appropriately sized, though the opening 'Read-only' largely duplicates the annotation rather than adding new behavioral detail.

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 return-value explanation is not required. However, for a four-parameter tool with 0% schema description coverage, the description leaves `limit` undocumented and does not specify how `query` is interpreted or whether multiple kinds are possible.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate. It explains the four `kind` values and maps `query` to contacts and `days` to calendar, but `limit` is never mentioned and the `query` matching rules remain unspecified.

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?

The description makes clear that the tool retrieves four kinds of local information: location, calls, contacts, and calendar. It is more specific than the vague name 'info', but it does not distinguish this tool from siblings like map or phone and lacks an explicit verb such as 'retrieve'.

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?

The description provides no guidance on when to use this tool versus alternatives such as map, phone, or messages. It only lists what each `kind` returns, leaving routing decisions entirely to inference.

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

Deploy Server