BatterySnap

Fleet battery summary

fleet_summary

Read-onlyIdempotent

Aggregate battery metrics across the entire fleet, or across one brand when brand is provided, optionally restricted to one country / continent. Returns mean / median / p25 / p75 / min / max for the same set of metrics as model_summary. Use this for fleet-wide baselines that a single device or model can be compared against. A region scope with fewer than 5 devices is refused; to compare several regions at once use region_summary.

Input Schema

Name	Required	Description
`brand`	No	Optional lowercase brand identifier. If set, aggregates across that brand only; otherwise across the entire fleet.
`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.

Output Schema

Name	Required	Description
`scope`	No	'fleet' for the whole fleet, else the comma-joined filters applied, e.g. 'brand:samsung', 'country:FR' or 'brand:samsung,continent:Asia'.
`awake_ratio`	No
`model_count`	No	Distinct resolved models in scope.
`device_count`	No	Distinct devices in scope.
`temperature_c`	No
`snapshot_count`	No	Sum of snapshots across all devices in scope.
`ac_charge_hours`	No
`discharge_hours`	No
`usb_charge_hours`	No
`battery_level_pct`	No
`wireless_charge_hours`	No

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."
+}

changedOutput schema / properties / scope / description

Previous value: -"'fleet' for whole fleet, or 'brand:<lowercase-brand>' when scoped to a brand."New value: +"'fleet' for the whole fleet, else the comma-joined filters applied, e.g. 'brand:samsung', 'country:FR' or 'brand:samsung,continent:Asia'."

First observedOct 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), but the description adds real behavioral context beyond them: the minimum-5-device refusal rule and the fact that region is derived from device time-zone settings rather than GPS/IP. It stops short of covering cost/latency or what happens with an unrecognized brand or country value.

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?

Four tight sentences with no filler: scope first, return values second, intended comparison use third, refusal and alternative last. Each sentence carries a distinct decision-relevant fact.

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?

With an output schema present, the description needn't spell out the payload; it instead spends its budget on scope, the refusal precondition, and sibling routing. Nothing an agent needs to call this correctly is missing.

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 the per-parameter meaning of brand, country and continent is fully documented in the schema, including the time-zone derivation and the country/continent intersection. The description mostly restates that filtering hierarchy; its only addition beyond the schema is that the 5-device refusal applies to region scope.

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?

Specific verb+resource ('aggregate battery metrics across the entire fleet') with explicit scope modifiers (brand, country/continent) and the returned statistics set. It names model_summary as the metric-parallel sibling, so an agent can tell it apart from the other summary tools without opening the schema.

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?

States the intended use ('fleet-wide baselines that a single device or model can be compared against') and gives an explicit exclusion with an alternative: 'to compare several regions at once use region_summary'. It also states a precondition that blocks invocation (region scope under 5 devices is refused).

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?