Skip to main content
Glama

phone_notifications

Retrieve notifications received on an Android phone since the bridge service started, including app, text, and time, newest first, with optional limit and clear controls.

Instructions

Notifications that arrived on the phone since the Agent Bridge service started (app, text, time), newest first.

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

Input Schema

NameRequiredDescriptionDefault
clearNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the list is a bounded snapshot (service start onward) and ordered newest first, but says nothing about the `clear` parameter, which strongly implies a destructive state change (dismissing/clearing notifications) that is never acknowledged or qualified.

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?

A single compact sentence with the resource and ordering front-loaded and no wasted words. The parenthetical field list is efficient, though it uses space on return shape that could have gone to the undisclosed parameters.

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?

For a two-parameter tool with no annotations and no output schema, the description omits critical facts: what `clear` does and whether it is irreversible, how `limit` behaves and what the default is, and whether the result is ever truncated. Return fields are partially covered, but the input behavior an agent must reason about is not.

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 description coverage is 0% for both parameters, so the description must compensate and does not. Neither `limit` (truncation of the list) nor `clear` (apparent destructive behavior) is explained; the parenthetical (app, text, time) describes response fields, not inputs, so it does not help an agent set either parameter.

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?

Names a specific resource (phone notifications) and bounds it precisely: only notifications that arrived since the Agent Bridge service started, returned newest first, with the tuple (app, text, time). The read/listing intent is implicit rather than stated by a verb, but an agent can immediately tell what it gets back.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the many other phone_* tools. The 'since the service started' scoping is a useful hint about coverage but is framed as a limitation of the data, not as usage advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.