Skip to main content
Glama
pironjulien

NexusAndroid

by pironjulien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

info

Read-onlyIdempotent

Read last known Android location, recent calls, contact numbers by name, or upcoming calendar events. Use this read-only query to inspect phone data without changes.

Instructions

Lecture seule. location : dernière position connue (précision, âge, lien Maps). calls : derniers appels (reçus, émis, manqués). contacts : numéros d'un nom (query). calendar : agenda des days prochains jours.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo
kindYes
limitNo
queryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYes
textYes
callsNo
eventsNo
contactsNo
locationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • 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"
+}
  2. First observedv0.3.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and 'Lecture seule' merely restates the read-only annotation. The description does add useful content-level context (what each kind returns, e.g. accuracy/age/Maps link, received/outgoing/missed call types), which goes beyond the annotations. No auth, rate-limit, or failure behavior is described, but that bar is lower given the annotation coverage.

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 compact sentence with the read-only qualifier front-loaded, followed by a tight per-kind listing with no filler. Every clause maps to a distinct mode and earns its place, though the enum-legend format is slightly dense.

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?

An output schema exists, so return values need not be explained, and the description adequately covers the dispatcher's modes. The gaps are the undocumented `limit` parameter and the absence of routing guidance against similar siblings, which are minor given the schema and annotations.

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 description coverage is 0%, so the description must carry parameter meaning, and it does for three of four: `kind` (all four enum modes explained), `query` (a name for contact lookup), and `days` (calendar horizon). Only `limit` is left undefined, so it substantially compensates for the coverage gap without being complete.

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 functions as a legend for the `kind` enum, stating exactly what each mode returns (last known position, recent calls, numbers for a name, upcoming calendar). This gives an agent a clear picture of the tool's scope even though the name `info` itself is generic. It does not, however, differentiate from overlapping siblings such as `messages`, `notifications`, or `phone`.

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?

Usage is implied by the per-kind breakdown, so an agent can infer that `kind=contacts` + `query` is for looking up a number, and `kind=calendar` is for an agenda. But there is no explicit when-to-use guidance and no mention of alternatives among the many siblings (messages, notifications, phone), leaving routing ambiguous.

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