Skip to main content
Glama

adb_thermal_snapshot

Captures thermal and power data—thermal zones, CPU frequencies/governors, cooling states, and battery temperature/current—to diagnose overheating or power drain. Save a baseline for later comparison.

Instructions

Capture a thermal and power snapshot: all thermal zone temperatures, per-CPU frequencies and governors, cooling device states, and battery temperature/current draw. Optionally save as a baseline for later comparison.

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

Input Schema

NameRequiredDescriptionDefault
saveNoSave snapshot as a baseline JSON file
labelNoLabel for saved baselinesnapshot
deviceNoDevice serial

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, the description carries the full behavioral burden. It does disclose the one real side effect (writing a baseline JSON file) and that the operation reads a broad set of kernel/sysfs data, but it says nothing about permissions, whether some fields may be unavailable on non-rooted devices, latency, or error behavior.

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, front-loaded with the action, the payload enumerated in a single readable list, and the optional save capability placed last. No filler or restated title.

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 no-output-schema capture tool, enumerating what the snapshot contains is exactly the right compensation, and the save option is covered. Remaining gaps are the on-device path/format of the saved baseline and how it is later consumed, which would let an agent chain into the comparison tool without guessing.

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 100%, so the schema already documents save, label, and device. The description adds only a light gloss on save/label ("baseline for later comparison"), which roughly restates the schema text "Save snapshot as a baseline JSON file"; it adds nothing about device selection semantics or label collision behavior. 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?

"Capture a thermal and power snapshot" gives a specific verb and resource, and the enumeration (thermal zones, per-CPU frequencies/governors, cooling devices, battery temp/current) makes the scope concrete and distinguishable from siblings like adb_battery or adb_perf_snapshot. It stops short of naming those siblings outright, so an agent still has to infer the boundary itself.

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?

"Optionally save as a baseline for later comparison" implies the intended workflow leading to adb_thermal_compare, but never states it. There is no explicit when-to-use versus adb_battery / adb_perf_snapshot / adb_health_check guidance and no stated preconditions (e.g., root needed for governors or cooling device states).

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