Skip to main content
Glama
Sign In
adb-tv-mcp

adb-tv-mcp

by mosesmrima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

adb_getprop

Read device properties from Android devices via ADB. Filter by substring to get specific system or hardware information.

Instructions

Read device properties (all, or filter by substring).

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": "adb_getprop"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNo
serialNodevice serial (host:port); omit if only one device

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It correctly implies a read-only operation, which matches adb semantics, but provides no detail on output format, whether properties are system/device-specific, or behavior when a filter matches nothing. The read-only implication is reasonably clear from 'Read device properties'.

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?

A single, front-loaded sentence: 'Read device properties (all, or filter by substring).' Every word earns its place, with no fluff or repetition.

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?

For a read-only property-listing tool with 2 optional parameters and no output schema, the description is close to adequate. It covers the main function and filter option but omits what the return looks like, which matters since there's no output schema to communicate that.

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 50%; the 'serial' parameter is documented in the schema while 'filter' is not. The description adds meaning to 'filter' (filter by substring) which helps. However, no detail on filter syntax (case sensitivity, prefix vs substring matching) or on filter matching multiple properties.

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 states a clear action ('Read device properties') with an explicit resource (device) and scoping option (all or filter by substring). It distinguishes this from siblings like adb_settings (settings vs generic properties) and adb_shell, though it doesn't explicitly name which sibling to prefer for property reads vs other reads.

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 on when to use this vs alternatives. With 23 sibling adb tools ranging from screenshots to settings to shell, an agent has no basis to distinguish reading device properties from adb_settings or adb_shell. No mention of required device connection state or when the filter is appropriate.

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