Skip to main content
Glama
Sign In
android-device-mcp

android-device-mcp

by prashant1507
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get network details

get_network_details

Retrieve Wi-Fi and network information for an Android device by providing its serial number.

Instructions

Retrieve network, Wi-Fi information for an Android device by serial number.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "serial": "<serial>"
    },
    "name": "get_network_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
serialYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states a read operation, but does not mention any side effects, permissions required, or performance characteristics. The description adds minimal insight beyond the purpose.

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?

The description is a single, clear sentence with no extraneous information. It is front-loaded and concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having only one parameter and no output schema, the description is too minimal. It does not specify what network information is returned (e.g., SSID, IP, signal strength) or any error conditions. An agent cannot fully understand the tool's behavior or output.

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

Parameters2/5

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

Schema coverage is 0%, so the description should explain the 'serial' parameter meaning. It merely mentions 'by serial number' without format, source, or constraints. The schema already indicates it's a required string, so the description adds no value.

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

Purpose5/5

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

The description clearly states the tool retrieves network/Wi-Fi information for an Android device by serial number. The verb 'Retrieve' and resource 'network, Wi-Fi information' are specific. It distinguishes from sibling tools like clear_device_logs or take_screenshot.

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?

No guidance is provided on when to use this tool versus alternatives, such as get_device_logs or get_app_details. It does not mention prerequisites or scenarios where it might be inappropriate.

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