BatterySnap

Rank models by metric

top_models

Read-onlyIdempotent

Rank device MODELS by any battery metric, aggregating across every device of that model. This is the tool for 'which phone model has the best battery life', 'which models charge fastest', 'which run hottest' — questions that would otherwise need one model_summary call per model.

Ordering is by the per-model MEDIAN of the metric (outlier-resistant); the mean is returned alongside. Use brand to rank within one manufacturer and min_devices to require a minimum sample size. country / continent rank the models as they behave in one region (e.g. heat in hot climates).

Input Schema

Name	Required	Description	Default
`brand`	No	Optional lowercase brand filter. When omitted, devices from any brand are ranked together.
`limit`	No	Number of devices to return, 1..100.
`order`	No	'desc' (default) ranks the highest values first, 'asc' the lowest. Pick the direction that matches the question: fastest charging is ac_charge_hours + asc; longest battery life is discharge_hours + desc.	desc
`metric`	Yes	Which battery metric to rank on. One of: 'temperature_c' (mean battery temperature, C), 'max_temperature_c' / 'min_temperature_c' (hottest / coldest ever seen, C), 'battery_level_pct' (mean charge level, 0-100), 'discharge_hours' (hours to drain a full 100% - HIGHER means longer battery life), 'ac_charge_hours' / 'usb_charge_hours' / 'wireless_charge_hours' (hours to charge a full 100% on that source - LOWER means faster charging), 'awake_ratio' (fraction of time awake / screen-on, 0..1), 'snapshot_count' (how much data the device contributed), 'uptime_hours' (longest single uptime between reboots).
`country`	No	Optional ISO 3166 alpha-2 country code (e.g. 'FR', 'IN', 'US'), case-insensitive. Keeps only devices whose time zone belongs to that country. The region comes from the phone's time-zone setting, not GPS / IP.
`continent`	No	Optional continent, case-insensitive: 'Africa', 'Antarctica', 'Asia', 'Europe', 'North America', 'Oceania' or 'South America'. Keeps only devices whose time zone lies there. Combine with `country` for an intersection.
`min_devices`	No	Ignore models backed by fewer devices than this. Defaults to 3 so a single outlier phone cannot win a ranking. Raise it for more robust comparisons. Raised to at least 5 when a region filter is set.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026

addedInput schema / properties / continent

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional continent, case-insensitive: 'Africa', 'Antarctica', 'Asia', 'Europe', 'North America', 'Oceania' or 'South America'. Keeps only devices whose time zone lies there. Combine with `country` for an intersection."
+}

addedInput schema / properties / country

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional ISO 3166 alpha-2 country code (e.g. 'FR', 'IN', 'US'), case-insensitive. Keeps only devices whose time zone belongs to that country. The region comes from the phone's time-zone setting, not GPS / IP."
+}

changedInput schema / properties / min_devices / description

Previous value: -"Ignore models backed by fewer devices than this. Defaults to 3 so a single outlier phone cannot win a ranking. Raise it for more robust comparisons."New value: +"Ignore models backed by fewer devices than this. Defaults to 3 so a single outlier phone cannot win a ranking. Raise it for more robust comparisons. Raised to at least 5 when a region filter is set."

First observedOct 16, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so safety is covered. The description adds genuinely useful behavior: ordering is by per-model MEDIAN (outlier-resistant) with the mean returned alongside, and min_devices defaults to 3 to prevent a single outlier phone from winning. It stops short of 5 only because output shape and any performance/pagination characteristics are left to the output schema.

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?

Front-loaded with the core verb/resource, then the decision rule, then the ordering semantics and parameter guidance. Every sentence carries information an agent needs; there is no filler or restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter ranking tool with a full output schema, the description covers purpose, alternatives, aggregation method, outlier handling, and region-filter interactions. Nothing an agent needs in order to choose and call this tool correctly is missing, and return values are correctly delegated to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description clears that bar by framing what the filters mean in practice (brand = rank within one manufacturer; country/continent = models as they behave in one region, e.g. heat in hot climates) and by explaining the min_devices rationale. It does repeat some schema content (order direction examples, region-raised floor), which keeps it from a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (rank) and resource (device MODELS), plus the aggregation semantics (per-model median across all devices of that model). It explicitly distinguishes itself from model_summary by naming the per-model-call alternative it replaces, and from device_ranking/top_devices by operating on models rather than devices.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete question patterns ('which phone model has the best battery life', 'which charge fastest', 'which run hottest') and the explicit alternative ('would otherwise need one model_summary call per model'). It also tells the agent when to use brand, min_devices, and country/continent, including the tricky heat-in-hot-climates case.

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

All BatterySnap tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?