Skip to main content
Glama
pironjulien

NexusAndroid

by pironjulien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

settings

Idempotent

Reads or updates Android phone options like Wi-Fi, Bluetooth, data, location, NFC, DND, brightness, and volume, then rechecks the resulting state.

Instructions

Réglages du téléphone, réversibles : sans value, lit l'état ; sinon le change puis le relit. wifi/bluetooth/data/location/nfc : on|off (couper le Wi-Fi est refusé quand la liaison passe par lui). dnd (ne pas déranger) : on|off|priority|alarms. brightness : 1-100 (%) ou auto. volume : 0-100 (%, médias).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
valueNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
textYes
valueYesvaleur relue sur le téléphone après le changement éventuel
changedYestrue si une valeur a été demandée (changement envoyé, puis relu)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "changed": {
+      "description": "true si une valeur a été demandée (changement envoyé, puis relu)",
+      "title": "Changed",
+      "type": "boolean"
+    },
+    "name": {
+      "title": "Name",
+      "type": "string"
+    },
+    "text": {
+      "title": "Text",
+      "type": "string"
+    },
+    "value": {
+      "description": "valeur relue sur le téléphone après le changement éventuel",
+      "title": "Value",
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "value",
+    "changed",
+    "text"
+  ],
+  "title": "SettingResult",
+  "type": "object"
+}
  2. First observedv0.3.1

TDQS

A4/5.0
Behavior4/5

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

Annotations say readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds valuable nuance: changes are reversible, and reading happens after change. It also discloses a specific refusal condition for Wi-Fi. That's meaningful behavioral context beyond annotations.

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 structured in a few dense lines: purpose, then a per-setting value legend. It's front-loaded with the read/write behavior. Slightly terse and mixing French/English terms, but every sentence carries information.

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?

With an output schema present, return values needn't be described. The description gives enough for an agent to call correctly: when to read vs write, allowed values per setting, and a key constraint. It could be more complete about error handling for invalid values, but it's solid for a simple 2-param tool.

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 compensate. It does: it explains the 'name' enum semantics for each setting and gives value formats/ranges (on/off, 1-100%, auto, 0-100%, dnd modes). Only gap: it doesn't explicitly map each format to each enum name, but it's inferable.

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 clearly states this tool controls phone settings (read or modify) — a specific verb+resource. It's distinguishable from siblings like info or phone. The dual read/write behavior is explicitly stated ('sans value, lit l'état ; sinon le change puis le relit').

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

Usage Guidelines4/5

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

The description explains when to read vs write based on the presence of the 'value' parameter. It also gives a specific constraint: cutting Wi-Fi is refused when the connection goes through it. However, it doesn't mention alternatives or when not to use the tool for other settings not listed.

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