Skip to main content
Glama

adb_notifications

Read active Android notifications and extract package, title, text, importance, channel, and flags to verify push delivery, monitor notification state, and test notification features.

Instructions

Read active notifications on the device. Parses the notification manager dump to extract package, title, text, importance, channel, and flags for each notification. Useful for verifying push notification delivery, monitoring notification state, and testing notification-related features.

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_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
filterNoFilter by package name (partial match, case-insensitive)
maxResultsNoMaximum notifications to return (1-50, default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does convey that this is a pure read (no mutation) and that results are derived by parsing a notification-manager dump, which usefully implies the data is a snapshot of currently active notifications only. It does not say what happens with zero notifications, whether dismissed/ongoing notifications are included, or whether any device-side permissions/root are needed.

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?

Three short sentences, front-loaded with the action and scope, then the return fields, then use cases. No redundant or filler wording; the only mild loss is that the return-field sentence could be read as padding given there is no output schema to rely on.

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?

The tool is simple (3 optional params, no nested objects, no output schema) and the description covers what it does and what fields come back. Still missing for full completeness: the 'active notifications only' snapshot caveat, empty-result behavior, and any environment prerequisites, which matter for a dump-parsing read tool.

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 100%, so all three parameters (device, filter, maxResults) are already documented in the schema including the partial/case-insensitive match semantics. The description adds no parameter-level meaning, leaving this at the baseline for full schema coverage.

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?

States a specific verb and resource ('Read active notifications on the device') and adds the mechanism ('Parses the notification manager dump') plus the exact fields extracted. It is clearly not one of the many shell/file/UI siblings, though it never names a neighbor like adb_dumpsys or adb_logcat as the alternative for notification debugging.

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?

The third sentence gives three concrete use contexts (verifying push delivery, monitoring state, testing notification features), which implies when to call it. It gives no exclusions, prerequisites (device connected, permission), or alternatives for cases where notifications aren't visible this way.

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