Skip to main content
Glama

phone_web_search

Run a web search directly on an Android phone by opening the default search app or browser for the submitted query.

Instructions

Run a web search on the phone (opens the default search app or browser).

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": {
      "query": "<query>"
    },
    "name": "phone_web_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

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?

With no annotations, the description carries the full burden. It does disclose the important behavioral fact that this launches an external app/browser rather than performing the search in-process, which sets expectations correctly. However, it says nothing about whether any results are returned, whether the device must be unlocked, or whether the app is brought to the foreground.

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 short sentence with the action front-loaded and a parenthetical that adds genuinely new information rather than restating the name. Nothing is wasted.

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 simple one-parameter action tool with no output schema, most of what an agent needs is present, particularly the fact that it delegates to an external app. It still leaves open what the call returns and any preconditions, which matters because the agent cannot otherwise tell whether to expect data back.

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?

One parameter at 0% schema description coverage, so the description must compensate. "Web search" implies the query is free-text search terms, but it does not specify whether a URL or search-operator syntax is accepted, nor any length or encoding constraints.

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 ("Run a web search on the phone") and the parenthetical clarifies the mechanism: it launches the default search app or browser. That distinguishes it from a data-returning search and from generic app launching, though it does not name sibling tools like phone_open_link explicitly.

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?

There is no when-to-use or when-not-to-use guidance. The agent is not told to prefer phone_open_link for a known URL, nor whether this tool should be used when the agent needs actual search results versus merely launching an app on the device.

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