Skip to main content
Glama

adb_thermal_compare

Compare a device's current thermal and power state with a saved baseline to see temperature, CPU frequency, and battery drain changes.

Instructions

Compare current thermal/power state against a saved baseline. Reports temperature changes per zone, CPU frequency shifts, and battery drain rate differences.

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

Input Schema

NameRequiredDescriptionDefault
deviceNoDevice serial
baselinePathNoPath to baseline JSON. If omitted, uses the most recent baseline for the device.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv1.1.3
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden. It usefully discloses what the comparison reports (per-zone temperature deltas, CPU frequency shifts, battery drain rate differences), but it does not state that the operation is read-only, whether it captures a new snapshot as part of the call, or what happens when no baseline exists for the device.

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 sentences, zero filler. The core action is front-loaded and the second sentence covers the return content, so every clause earns its place.

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?

There is no output schema, but the description effectively summarizes the return payload, which is the most important gap to close for this tool. Only the precondition of an existing baseline and its failure behavior are left unstated, so it is nearly complete for a two-optional-parameter read/comparison tool.

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%, so both parameters (device, baselinePath) are already documented, including the most-recent-baseline fallback. The description adds no additional meaning about parameter behavior, so the baseline 3 applies.

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 (compare) and a specific resource (current thermal/power state vs. a saved baseline), then enumerates the three reported deltas. It is clearly distinguishable from adb_thermal_snapshot or adb_battery_drain, though it never names those siblings 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?

The phrase 'against a saved baseline' implies this is a follow-up to a snapshot step, and the schema note about falling back to the most recent baseline reinforces that workflow. However, there is no explicit when-to-use/when-not guidance and no named alternative for the case where no baseline exists.

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

Deploy Server

Other Tools