Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

debug_ping

Verify the app is running and polling by round-tripping a ping through the in-app debug channel without changing focus.

Instructions

Round-trip a ping through the in-app debug channel. Proves the app is running and polling without touching focus.

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

Input Schema

NameRequiredDescriptionDefault
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 behavioral burden and does disclose a meaningful trait: it does not touch focus, so it is non-disruptive to the UI session. It does not say whether the call is read-only in effect, what happens on timeout, or what a failure looks like, leaving gaps for a diagnostic tool.

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 payoff, with no redundant wording. Every clause adds information.

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-optional-parameter diagnostic tool with no output schema, the description covers what it does and its key side-effect guarantee. Only failure/timeout behavior is unaddressed, a minor gap at this complexity level.

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?

The single timeout_ms parameter is fully documented in the schema (100% coverage) including its 10000ms default, so the schema does the work. The description adds no meaning about timeout behavior or what occurs when the timeout elapses, which is the baseline case.

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 concrete verb and resource (round-trip a ping through the in-app debug channel) and adds the effect it has (proves the app is running and polling). An agent can distinguish it from generic status tools by the 'without touching focus' qualifier, though no sibling such as debug_status is named explicitly.

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?

Usage is implied rather than stated: the description says the ping proves the app is running and polling without stealing focus, which suggests when it is appropriate. There is no explicit when-not guidance and no comparison to debug_status or debug_command, so the agent must infer the choice.

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