Skip to main content
Glama
Sign In
Ultimate Android MCP

Ultimate Android MCP

by oddlyspaced
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_serial_no

Retrieve the serial number of a connected Android device to identify it uniquely. Works without parameters for quick device verification.

Instructions

Returns the serial number of the connected Android device. No parameters are required.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_serial_no"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It accurately says the tool returns the serial number and requires no parameters, but it does not disclose behavior when no device is connected, the format of the returned value, or any error conditions.

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 two short sentences with no filler. Every word earns its place: the operation, the target, and the parameter expectation.

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?

For a zero-parameter read-only tool with no output schema, this description covers the essential information needed to invoke and interpret the call. Minor gaps around failure cases are not material for such a simple 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?

The input schema has zero properties and schema description coverage is 100%, so the baseline is 4. The description adds the explicit statement 'No parameters are required,' which clarifies that the tool is callable with an empty argument object.

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 operation ('Returns') and unique resource ('serial number of the connected Android device'), making the tool's purpose unmistakable even among device-info siblings such as get_battery_level, wm_density, and get_properties. The no-parameter note reinforces that this is a simple device identifier retrieval.

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 context is clear: use it to get the serial number of the connected Android device, and it requires no parameters. It does not explicitly explain when not to use it or name alternatives, but there are no closely interchangeable siblings for serial-number retrieval.

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