Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

phone_message

Deliver a phone-app message to the running app through the debug channel so the app handler stores it; use state_read to verify.

Instructions

Deliver a phone-app message to the running app through the debug channel and let the app handler store it. Use state_read to verify last_phone_message.

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

Input Schema

NameRequiredDescriptionDefault
bodyNoMessage body
titleNoMessage title
timeout_msNoTimeout in milliseconds (default: 10000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 mutation semantics ('let the app handler store it') and the transport path, implying a running app is required, but it says nothing about failure behavior when the app isn't running, what the timeout does on expiry, or whether repeated deliveries overwrite.

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 followed by the verification step. Nothing is redundant with the schema and no sentence is filler.

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 three-optional-parameter delivery tool with no output schema, the description covers what it does, the channel it uses, the side effect, and how to confirm the result via state_read. Only error/timeout behavior and the precondition of a running app are left implicit.

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% and all three parameters are documented inline, including the timeout default, so the baseline is 3. The description adds only the 'last_phone_message' state key as context, not additional meaning for body/title/timeout.

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 uses a specific verb+resource pair ('Deliver a phone-app message') and names the transport mechanism ('through the debug channel'), which separates it from generic siblings like debug_command or send_key. It stops short of explicitly contrasting itself with those siblings, so it lands at clear-but-undifferentiated rather than a 5.

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?

It gives one concrete follow-up workflow ('Use state_read to verify last_phone_message'), which tells the agent how to confirm the effect. It offers no guidance on when to prefer this over debug_command/debug_ping, nor any exclusions or prerequisites such as the app needing to be running.

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