Skip to main content
Glama

phone_dial

Open the Android dialer with a specified number pre-filled for manual call confirmation; it never places the call, so the user reviews and taps Call.

Instructions

Open the phone dialer with a number filled in. It never places the call; the user presses call. If several dialer apps are installed, Android shows "Complete action using": tap one.

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": {
      "number": "<number>"
    },
    "name": "phone_dial"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does real work: it states the call is never placed, that the user must press call, and that Android may surface a "Complete action using" chooser requiring a tap. That is exactly the non-obvious behavior an agent needs. It stops short of documenting permissions or exactly what the tool returns after the dialer opens.

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?

Two short sentences, front-loaded with the action and the critical non-action constraint, plus one practical aside about the app chooser. Nothing is redundant or padded.

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 one-parameter tool with no output schema and no annotations, the description covers the main behavioral risk (accidental call) and the interactive follow-up (chooser tap). Only the expected number format and the post-invocation outcome are left unspecified.

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 coverage is 0% for the single parameter, so the description must compensate. It does establish the parameter's role (the string placed into the dialer field) but gives no format guidance, such as whether punctuation, '+', or dialer characters like '*' and '#' are accepted.

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 opens with a specific verb and resource ("Open the phone dialer") and immediately scopes it as prefilling a number rather than dialing. It is clearly distinct from a generic app-launch tool, though it never names a sibling such as phone_open_app to make the contrast explicit.

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 use case is implied well: composing a number for the user to confirm. There is no explicit when-not guidance or named alternative for cases where the agent just wants to launch an app, so the agent must infer the boundary from the sibling list.

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